Affichage des articles dont le libellé est Bootloader. Afficher tous les articles

I didn't find a thread for the Volt, model LS740 on Virgin Mobile. Rooted by the original owner. So I'm posting it here. I'm using adb on Ubuntu.

So I'm trying to repair a broken system by reflashing the stock ROM. I suspect the previous owner(who rooted) may have removed multiple important system apps. Upon doing a factory reset it has no home launcher or keyboard. As soon as the screen turns off it loops a com.android.systemui has stopped. Every boot you need to do a factory reset to get it to work: booting once, then again will loop the systemui crash, requiring a factory reset to work.

The android recovery works, I can get to it, but it offers install update from cache, adb, or sd card. The phone will not recognize sd card while it is in recovery, and adb doesn't work in recovery, only while booted. Copying recovery image to cache fails at 71%, I suspect the phone does not have enough RAM to move 1.17 GB from A to B. The phone may also not have spare storage space. I'm working on finding an sd card so I can try copying from there.

"adb reboot bootloader" reboots the phone normally. If there's a bootloader it skips it entirely. I found threads that say uncheck fast boot in power/battery options, but I have no such check box.

Right now, I have adb, images/zips for twrp recovery and stock rom, and I can push apks for a launcher and keyboard. But I apparently can't access bootloader or install rom via recovery. I don't have an sd card to try and copy the rom to cache, which I will try as soon as I get a card.

Adb cannot run as root, I get "adbd cannot run as root on production builds. So I can't directly push the rom to /cache/backup using adb.

Any help? I tried to get it all out there so that you guys could help better. Thanks for reading all that.





So i actually know nothing about unlocking or breaking code for rooting, etc. But I'm curious about the process.
Most phones come with a locked bootloader, etc.. is it not possible to replace the hardware that stores the bootloader, operating system and replace with new hardware that has been programmed with a hacked bootloader, etc?





I have the latest build and android version and I want to root my phone.
I have searched through the threads and only found root for older versions.
Is there any root available for the latest build and android?

I know I can't "officially" unlock my bootloader but is there a hack to it.. maybe an "unofficial" way?

Sent from my SGH-I337M using XDA Free mobile app





Is this possible, or do I just have to suck it up and find a windows machine to unlock my BL? I'm already rooted and a P769 on 20h firmware.

If my Linux distro matters, I am Mint 17.1





Hi all. New poster and completely non-tech savy. Over the last few days I've been tinkering with my phone trying to learn about various roms and related. I had successfully flashed the CM11 update to my droid X but found that the OS was running extremely slow. example ( while trying to talk through hangouts it would take 2-3 seconds for each letter to not only to show up but also register so I could type my next letter.) This having been the case I tried to downgrade the OS to stock or some older rom. Since going through the steps I find myself in alot of trouble! I am now able to load stock recovery and bootloader only! I am unable to get into Twrp or CWM at all. The phone if loaded regularly will only go as far as the Motorola logo and no further. It will stay on that logo until the battery is taken out. I am unable to power down or reboot otherwise. Unfortunatley I am unable to supply official information like Build and the related but I can say before flashed to CM11 it was the standard Droid X 2.3.4.621 M810 and the CM 11 build was the most recent CM 11 (shadow) build as of 5/18/2015. I need help to load into Twrp or whatever I can do to just load past the motorola logo screen. Oh lastly, I have installed the Motorola Driver program but my computer doesnt seem to be able to find the connection. It does show on device manager and states it is fully upto date driver wise. However it isnt found in RSD Lite run as admin. PLEASE help and or let me know of any information you need to assist me further. Keep in mind though at this time the info i have access to is very limited because of the access i dont have to the phone.





Root(1)"][IMG="Root(2)[/IMG]

Well I found a new root method with BOOTLOADER CAUGHT do not know who did or the developer ...

First you need to enter this site:


http://www.kingroot.net/down

download the APK like the image below

download Mobile

install it

Then open it

and fasten on root.

Then go on playstore to download >> Root Checker to confirm.

and enjoy your root


Sorry for the bad English ...





Can anyone send me a link to download the bootloader. Can't find it anywhere





i have new bootloader and i wana know is it possible to flash 4.3 from cwm recovery?





I read in the GPE thread that it uses stock kernel, but I'm not confident enough because I can't find any way to directly compare that statement with what's currently being used. I'm using flashfire rather than a recovery so I am trying to avoid soft bricking. Any help would be appreciated.

At&t 5.0.1 Stock Lollipop rooted





I found this method while browsing XDA one day.
Basically, open up a Lollipop ROM, navigate to /META-INF/com/google/android/ and open the "updater-script" file using notepad, and remove this line "assert(getprop("ro.bootloader") == "0x4118" || abort("This package supports bootloader(s): 0x4118; this device has bootloader " + getprop("ro.bootloader") + "."););" Or something that looks like it. (You may have to extract and recompress the file to do this.) Doing this will bypass the bootloader check, meaning that if you have an older bootloader, the install script will still run.
The only obvious issue I see is a line that looks like a vertical tear when you initially boot your device, but locking and unlocking your phone will get rid of it. I heard that CDMA data won't work with this tweak, but I can't say for sure.
Thanks for reading my guide, let me know if you think there's any way I could make it easier to understand. Remember to click the like button if I helped.





Hi,

anyone can help me how to root unlocked D6603 with 5.0.2 ?
Is this possible without flashing custom kernel and recovery ?





Today my S6 duos has arrived.
Is a SM-G920FS unit.
can anybody tell me how to check if is bootloader unlocked/locked?





I am planning to unlock bootloader.Probably I need a code which is given by Sony .My question is that If ı get this code from Sony,ıs my device being out of warranty ?Maybe,in one stage I must enter my ımei number to get code,and technical service of my phone understand that I got this code ;so my device will never being in warranty.Am I right ?Later,If ı relock bootlader,ıs my device being in warranty ?





Hi all, I am new to the XDA Forums and was just wondering if anyone can help me out with some trouble I'm having with my Huawei Ascend G526-L22.
Over the past few weeks, I have been finding it very hard to gain access to the 16-digit bootloader unlock code (usually Hex). After endlessly contacting Huawei in frustration attempting to gain access to a code that they had supposedly been giving out, I am left with a soft bricked phone.
The reason my phone is soft bricked is because I had become impatient and decided to "Kingo-root" (third party software) my device and it has sent it into a "Boot-loop" (upon boot the Huawei Ascend logo is at an endless standstill with the bottom buttons lighting up after 30 seconds)
I have tried:
- Holding all Buttons (Vol Up+Vol Down+Power) simultaneously for over 2 minutes
- Taken battery out countless times, left it out for 2 minutes inbetween, left Huawei Ascend screen on overnight to drain
- Attempted the 16-digit key in Fastboot (Vol Down+Power) only to find "Unlock Failed! Invalid key!" in the top right of the screen.
- Using DC Locker to try and unlock the phone (Ascend G526 not listed in models)
- Using EmotionUI (online Huawei Unlocking software) to unlock (again, Ascend G526 not listed in models)
- Attempted Update.app via ADB
- Attempted Update.app through external storage (only have 64gb card, phone recognises up to 32gb)
- Wiped cache, wipe data/factory reset countless times in System recovery (Vol Up+ Power) still stuck in "bootloop"
I know that all I need to to is gain access to an unlocked bootloader and I can safely get the device up and running, and I find it truly frustrating that Huawei (even after being claimed to) "can't provide the code because we stopped doing it in 2012".
If anyone has any tips to lead me in the right direction, or even get my phone up and running again (bootloader doesn't have to be unlocked) it would be greatly appreciated!

Many thanks in advance,
-Ziggy.





I must have missed a step when I unlocked my XT1053 last year. I never did anything with it and assumed that because it gives the the caution screen when I turn it off and back on, that the bootloader is unlocked. However, now that I decided to get down and do stuff, it's telling me via third party apps that my phone isn't actually unlocked. There's no super user app or anything. Do I need to go through the unlocking process again? I'm on 4.4.4.





I Have try to unlock my phone bootloader...
But i decide to Relock it...
(Firmware XT1039_RETAIL-BR-EU-SS_4.4.4_KXB21.14-L1.56-1_cid12_CFC_1FF)

I got a comand like this:

"fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock"

(Using The Minimal ADB and Fastboot)
(My Device firmware have 4 System IMG Spacechunks.)

Log:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.164s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.297s]
finished. total time: 1.461s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.141s]
writing 'logo'...
OKAY [ 0.141s]
finished. total time: 0.281s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 1.022s]
finished. total time: 1.443s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.422s]
writing 'recovery'...
OKAY [ 1.022s]
finished. total time: 1.444s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (248267 KB)...
OKAY [ 7.931s]
writing 'system'...
OKAY [ 17.454s]
finished. total time: 25.384s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (248994 KB)...
OKAY [ 7.935s]
writing 'system'...
OKAY [ 15.417s]
finished. total time: 23.353s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (257391 KB)...
OKAY [ 8.205s]
writing 'system'...
OKAY [ 16.311s]
finished. total time: 24.518s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (20588 KB)...
OKAY [ 0.742s]
writing 'system'...
OKAY [ 13.748s]
finished. total time: 14.492s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (59132 KB)...
OKAY [ 1.949s]
writing 'modem'...
OKAY [ 2.892s]
finished. total time: 4.842s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.071s]
finished. total time: 0.073s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.068s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (710 KB)...
OKAY [ 0.123s]
writing 'fsg'...
OKAY [ 5.347s]
finished. total time: 5.471s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.113s]
finished. total time: 0.114s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.288s]
finished. total time: 0.289s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 17.622s

But OEM Lock says "Too many Links"
(The device Says "Locked", and restarted, and boot propely)

I Checked in Fastboot
Says "Device is LOCKED. Status Code: 2

Is really Locked?





first off, thanks for your time and reading this!

I have the Z2 LTE Tablet. it was on a carrier network, EE. I paid sim-unlock £17 so I could get it to all networks.
here's my problem, it's on all networks but the bootloader says "allowed: no" is there nothing I can do??????
I have tried flashing different firmwares etc and different regions (do I always set them up as UK?!) and I've had no luck!

what should I do?!?!?!?!!?!





I am running the soak test 5.1 for the Pure edition Moto X 2014 xt1095, and the bugs are annoying me (the location icon persistent on the status bar and the 'emergency calls only') and I was wondering if there is a way to downgrade back to 5.0 without unlocking my bootloader.





xperia l
've unlocked bootloader by following the instructions provided on unlockbootloader.sonymobile.com/instructions and the fastboot tool sad "OKAY". Now when I try to turn it on again, I see SONY and then XPERIA logo, and then Xperia colour animation on the screen. It's been like that for more than an hour, and to turn it off I needed to pull out the battery. PC companion doesn't recognize it . I've tried holding the volume up button while starting up (the logos) and holding down both volume buttons and nothing happened.
Is there any way to fix this?





Has anyone successfully unlock the bootloader on the Verizon Moto G XT1028??
I tried the Motorola website where I successfully unlocked the Moto X but I got an error. Is there any other way?