Related
Hi
I followed this tutorial (http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/) to root my Nexus S (GTi-9023). Like a bunch of other people on this site my phone got stuck on the "Google with a pad lock" boot screen (I should have come to xda first). So to get past this i downloaded the stock rom (from here: http://forum.xda-developers.com/showthread.php?t=1056062) and extracted boot.img and then flashed the stock boot image and booted with it as below.
>fastboot flash boot boot.img
>fastboot boot boot.img
This fixed fixed my booting problem and i then used rom manager to install clockwork recovery. I can boot into clockwork recovery from rom manager but not from fastboot. i get an android with an exclamation mark. Any idea why and/or how to fix this?
Thanks in advance.
boozelclark said:
Hi
I followed this tutorial (http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/) to root my Nexus S (GTi-9023). Like a bunch of other people on this site my phone got stuck on the "Google with a pad lock" boot screen (I should have come to xda first). So to get past this i downloaded the stock rom (from here: http://forum.xda-developers.com/showthread.php?t=1056062) and extracted boot.img and then flashed the stock boot image and booted with it as below.
>fastboot flash boot boot.img
>fastboot boot boot.img
This fixed fixed my booting problem and i then used rom manager to install clockwork recovery. I can boot into clockwork recovery from rom manager but not from fastboot. i get an android with an exclamation mark. Any idea why and/or how to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Rename /etc/install-recovery.sh to install-recovery.sh.bak, then reflash the recovery.
DONT use rom manager to flash the recovery it hardly ever works [for me],
If you have 'Android SDK' and 'ADB' then,Download a decent recovery file and place it in your 'Android-SDK/tools" directory, then go to your 'cmd' [command prompt] and navigate to your android-sdk/tools directory ,,example below.
''cd C:/android-sdk/tools'' [cd meaning 'change directory']
Then type, "adb devices" it should list your devices ith a load of numbers and letters, if it does then proceed, if not re-plug your device into the USB [in the bootloader]
Then type,
"fastboot flash recovery recovery.img" and let it do its thing. [if it does not work , make sure you renamed you recovery file to 'recovery.img'
Hope this helps!!
XDA_Badman said:
DONT use rom manager to flash the recovery it hardly ever works [for me],
...
Click to expand...
Click to collapse
The problem is that with the stock rom the stock recovery gets flashed after boot up (by /etc/install-recovery.sh). Search for install-recovery.sh in the nexus s forums.
Where can I find fastboot app and other apps that I need to flash the phone?
Thanks in advance!
vita94 said:
Where can I find fastboot app and other apps that I need to flash the phone?
Thanks in advance!
Click to expand...
Click to collapse
follow this
http://forum.xda-developers.com/showthread.php?t=1253476
Can I follow the tutorial to step 13.
I downloaded fastboot.exe and adb.exe with some dlls.
And then from step 14 use the http://forum.xda-developers.com/showthread.php?t=927379:
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
Can I install android like that, without using the exe setup wizard?
vita94 said:
Can I follow the tutorial to step 13.
I downloaded fastboot.exe and adb.exe with some dlls.
And then from step 14 use the http://forum.xda-developers.com/showthread.php?t=927379:
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
Can I install android like that, without using the exe setup wizard?
Click to expand...
Click to collapse
so i take it that you have flash kdz? and have swiftdroid stuff together with fastboot and adb and the dll in the same folder?
if yes then yea ur good to go with the commands
but since its ur first time make sure you have this in the folder
fastboot.exe
adb.exe
adbwinapi.dll
adbwinusbapi.dll
boot.img
system.img
recovery.img
if you got problems just post it here il be happy to help
vita94 said:
Can I follow the tutorial to step 13.
I downloaded fastboot.exe and adb.exe with some dlls.
And then from step 14 use the http://forum.xda-developers.com/showthread.php?t=927379:
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
Can I install android like that, without using the exe setup wizard?
Click to expand...
Click to collapse
Yes, as long you have those images in the same directory as the fastboot files.
jhonnyx1000 said:
Yes, as long you have those images in the same directory as the fastboot files.
Click to expand...
Click to collapse
do you think i should make a picture tut for him?? i have time
Thank you all for your time,
I have successfully flashed it!
Can you recommend me what should I do to improve system performance?
vita94 said:
Thank you all for your time,
I have successfully flashed it!
Can you recommend me what should I do to improve system performance?
Click to expand...
Click to collapse
YAY GRATS welcome to cm7 :3
as for improving performance use the v6 super charge script
http://forum.xda-developers.com/showthread.php?t=1126940
Are there direct links to apk files for:
1. Busybox Installer
2. Script Manager
Thanks in advance!
y not just download them from market ?? they are free
Yes but I don't have WiFi connection at the moment.
ok swiftdroid already has busybox installed so here is the apk for script manager
http://dl.dropbox.com/u/34103290/os.tools.scriptmanager_43.apk
this is battery calibration(charge the phone to 100% without stop and follow on screen instructions. do this cus most of us have problems with the rom after doing it its better)
http://dl.dropbox.com/u/34103290/com.nema.batterycalibration_1.apk
Nvflash-ICS Restore!
This guide will not provide information to install Nvflash-ICS as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
The second method to restore has been removed until further study can be done!
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
I have finished installing Nvflash but where are my files?
/sdcard/AndroidRoot/ - this is your internal sdcard
Click to expand...
Click to collapse
What files should I have?
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
Click to expand...
Click to collapse
Nvflash recovery and going back to ICS for a fresh start.
Use blobunpack to unpack a stock ICS blob. The blob is found by unzipping the stock ICS firmware twice.
You can find the ICS firmware at this link (9.4.3.30) (post #3).
[INDEX][18 April 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
Please give philos64 a thanks while there, without him you would have a very hard time finding these downloads if at all.
these files have to be in the folder with Nvflash
wheelie -r --blob blob.bin -created with Nvflash install
nvflash --resume --download 4 blob.EBT -created with blobunpack
nvflash --resume --download 10 blob.APP – created with blobunpack
nvflash --resume --download 6 blob.LNX – created with blobunpack
nvflash --resume --download 5 recovery.img-ICS twrp recovery image name
nvflash --resume --go
then press volume down to enter twrp, flash root, flash rom or whatever you wish
Click to expand...
Click to collapse
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
What is blobunpack?
Here are some links to download and explain use.
https://github.com/AndroidRoot/BlobTools
windows compiled blobtools - http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
There were no dates for the following information.
The current AndroidRoot.mobi bootloader versions are
Transformer Prime: 9.4.2.28r01
Transformer TF300: 9.4.3.30r01
Transformer TF700:9.4.5.30r01
ChangeLog:-
Patch: Enable ‘fastboot boot’ command (removes ‘fastboot continue’, use ‘fastboot reboot’ instead).
Patch: Force unlocked state (protect your unlock status no matter what happens to your token).
Patch: Remove blob requirement from ‘fastboot flash’ (Flash the raw images (example: ICS_recovery.img) and not blob files).
Click to expand...
Click to collapse
When failing to get into APX mode you can try the following suggestions.
Special thanks to wha2do and daws for their input!
Also wha2do has posted a guide to enter APX that provides detail not found here! Please see his guide and give proper thanks if you find it helpful!
http://forum.xda-developers.com/show...3#post36159253
1.To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2.fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store. You must be rooted for this to work.
or
6. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.You should now be in APX mode.
Thanks for the help daws.
or
Only if there is no other resort!
7. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
Click to expand...
Click to collapse
Good Luck!
Click to expand...
Click to collapse
Due to my dock smoking my motherboard I have purchased a new motherboard and luckily it came as 4.0.3 ICS.
I now have installed and use Nvflash on my tablet.
In case anyone is interested this is the unit I purchased.
The box shows - Manufacturer's Reconditioned Parts - 90 Day Limited Warranty.
Usefull guide
Good work and helpfull guide for xda members :good:
Nice stuff
philos64 said:
Good work and helpfull guide for xda members :good:
Nice stuff
Click to expand...
Click to collapse
Thank you for your kind words.
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
chanhny said:
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
Click to expand...
Click to collapse
No.
The files contain device-specific keys and cannot be used for other devices.
See the original thread for details:
[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!
There's something I've not been quite clear about with NVFlash.
So I do my backup and keep my files.
Afterwards I upgrade to Jelly Bean (because I need the JB bootloader for ROM's right?), put TWRP recovery on, and flash a new ROM that uses the bootloader version I have.
So now I have the JB bootloader, can I still enter APX mode and do a restore, or do I have to remain on ICS bootloader to do a restore?
Is NVFlash truly unbrickable? A glance at this forum shows loads of bricks, would this have sorted their problem if they backed-up first?
Thanks!
tobdaryl said:
This guide will not provide information to install Nvflash as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
I have finished installing Nvflash but where are my files?
What files should I have?
Nvflash recovery and going back to ICS for a fresh start.
What is blobunpack?
Caution
Caution
There were no dates for the following information.
When failing to get into APX mode you can try the following suggestions.
Caution
Full brick recovery
Caution
Good Luck!
Click to expand...
Click to collapse
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
graphdarnell said:
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
Click to expand...
Click to collapse
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
tobdaryl said:
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
Click to expand...
Click to collapse
Not really. I didn't touch it. I'll do it again today to see. Thanks for the reply.
No recovery
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
waynestatemac said:
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
Click to expand...
Click to collapse
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
tobdaryl said:
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
Click to expand...
Click to collapse
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
waynestatemac said:
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
Click to expand...
Click to collapse
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
tobdaryl said:
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
Click to expand...
Click to collapse
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
waynestatemac said:
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
Click to expand...
Click to collapse
The first thing you flash in this guide is the bootloader. nvflash --resume --download 4 blob.EBT
With nvflash you can flash only what is needed for your situation. If you feel the problem is the bootloader you can flash just that and try again.
What you describe sounds like stock recovery is still working on your tablet. If flashing the bootloader does not help I would use stock 9.4.3.30, unzip once and place the remaining zip on your internal sdcard. You may get an update notification. Accept it and let your tablet do the work. If you don't get the notification reboot your tablet and you should see it then. Doing this will write stock bootloader, recovery, etc.
Stock recovery is the blob.SOS when you blobunpack. Just use the stock 9.4.3.30 blob and use the resulting SOS (recovery.img).
TF300T Bricked accessible using APX Mode.
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
NaderALDirany said:
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
Click to expand...
Click to collapse
I have read your previous posts in addition to this one.
There are four vehicles to restore your tablet. (some things can be done within android but you have no access)
1. recovery - stock or twrp
2. fastboot
3. adb
4. nvflash
I notice you also posted in my guide for accessing adb, fastboot, and apx. You were unable to access fastboot, adb, or recovery with those methods.
I don't know of any way to recover through apx without nvflash previously installed and you have no access to the other three methods.
Needs Stickied ... thanks man you helped save my butt :good:
Trigger911 said:
Needs Stickied ... thanks man you helped save my butt :good:
Click to expand...
Click to collapse
Thanks! *I'm glad you found the info useful.
Good morning,
I followed the tutorial here on XDA on how to basically factory reset my Nexus 7. Unfortunately, while going through all the steps I also deleted my recovery. Now I am unable to flash any recovery back on my device. I have tried flashing Clockwork, TWRP and even Google Stock recovery, but it won't work. Neither flashing via Nexus 7 toolkit nor by hand was successful, instead it always returns the following error message:
Booting into Android using an Insecure Boot Image..
cannot load "root\boot-insecure-.img' : No error
Now my Nexus 7 is in some random state, since Android 4.2.2 is installed, but rooting via the Toolkit returns the same message when it comes to the point of flashing a recovery. Then it simply skips the remaining steps and does not install the superuser app. I also downloaded and tried using the ROM Manager, but since root-access is missing, it can't do anything either.
Do you guys have any solution to this?
Help is very much appreciated!
Thanks!
marcfeld said:
Good morning,
I followed the tutorial here on XDA on how to basically factory reset my Nexus 7. Unfortunately, while going through all the steps I also deleted my recovery. Now I am unable to flash any recovery back on my device. I have tried flashing Clockwork, TWRP and even Google Stock recovery, but it won't work. Neither flashing via Nexus 7 toolkit nor by hand was successful, instead it always returns the following error message:
Booting into Android using an Insecure Boot Image..
cannot load "root\boot-insecure-.img' : No error
Now my Nexus 7 is in some random state, since Android 4.2.2 is installed, but rooting via the Toolkit returns the same message when it comes to the point of flashing a recovery. Then it simply skips the remaining steps and does not install the superuser app. I also downloaded and tried using the ROM Manager, but since root-access is missing, it can't do anything either.
Do you guys have any solution to this?
Help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Though toolkits save a lot of time, I always prefer to do stuff the manual way and I suggest you do the same. To flash the recovery do the following steps
1) a) if you are running Windows open cmd as administrator and CD into a folder containing adb and fastboot .exes
b) copy paste a downloaded recovery image in the same folder and rename it to recovery.img for simplicity.
2) boot into boot loader by pressing power volume down and volume up all together after the device is turned off
3) in bootloader enter the fastboot mode and in cmd on PC type
Code:
fastboot devices
At this moment your device should turn up in the command prompt.if it doesn't then try installing the Asus drivers and repeat the steps above carefully.
4) once all that is over type
Code:
fastboot flash recovery recovery.img
And then the recovery must be flashed . you will get an output on cmd with the time taken to flash it too .
Then reboot into recovery and enjoy.
A succinct summary, Red Devil.
I always maintain, on a my Windows laptop, a folder called FastBootAdb, that contains the following files...
fastboot.exe
adb.exe
AdbWinApi.dll (needed by Windows)
AdbWinUsbApi.dll (needed by Windows)
If I wish to flash a new recovery.img (or a new boot.img - useful for certain kernels, that consists of nothing but a boot.img, like franco for example. Most custom kernels though, consist of more than just a boot.img, and need to flashed via TWRP or CWM, and can't just be fastboot flashed).
Anyway... I just copy the new recovery into this folder, rename it to recovery.img and run the fastboot command accordingly...
Code:
fastboot flash recovery recovery.img
...similarly with the boot partition...
Code:
fastboot flash boot boot.img
To be honest, I'm puzzled why people feel the need to overcomplicate this very simple procedure with toolkits.
Rgrds,
Ged.
Thanks a million guys!
I will try this as soon as I get home tonight and let you know.
nourtsW escape
This did the trick!
Thanks again guys!
marcfeld said:
This did the trick!
Thanks again guys!
Click to expand...
Click to collapse
Glad you got it sorted.
With Android, there's always 'more than one way to skin a cat!'.
Rgrds,
Ged.
GedBlake said:
Glad you got it sorted.
With Android, there's always 'more than one way to skin a cat!'.
Rgrds,
Ged.
Click to expand...
Click to collapse
I am so relieved, because I thought I had bricked it...
GedBlake said:
A succinct summary, Red Devil.
I always maintain, on a my Windows laptop, a folder called FastBootAdb, that contains the following files...
fastboot.exe
adb.exe
AdbWinApi.dll (needed by Windows)
AdbWinUsbApi.dll (needed by Windows)
If I wish to flash a new recovery.img (or a new boot.img - useful for certain kernels, that consists of nothing but a boot.img, like franco for example. Most custom kernels though, consist of more than just a boot.img, and need to flashed via TWRP or CWM, and can't just be fastboot flashed).
Anyway... I just copy the new recovery into this folder, rename it to recovery.img and run the fastboot command accordingly...
Code:
fastboot flash recovery recovery.img
...similarly with the boot partition...
Code:
fastboot flash boot boot.img
To be honest, I'm puzzled why people feel the need to overcomplicate this very simple procedure with toolkits.
Rgrds,
Ged.
Click to expand...
Click to collapse
ive done this exactly step by step and i getthe system cannot find the specified path i made a folder inside the windows folder i named it recovery in the command prompt i did cd windows then cd recovery then i typed fastboot devicesthen it said that
Help! Nexus 7 won't accept recovery flash image
I've tried all the above. I can get to the command prompt, and fastboot devices sees my device. I input the above commands to reflash, it starts with message "sending 'recovery' <xxx.xkb>' then nothing. It just sits there until I reset or reboot my nexus 7. Can anyone help?
I instaled persona78's B600 mod on TWRP 3.0.2-0 and rebooted. Just boot logo. Nothing else. No recovery, no fastboot, nothing. After struggling a bit I mamaged to get into fastboot, but when I run adb command in Windows 8.1 it says "waiting for device" and that's it. I tried several tools and "kits" with more functions, one of them being TWRP.
Please help! Tommorow morning I have a working trip and I extremely need my phone, and in my country it's already 1:00 a.m.
I will be very thankful for any solution and fast response.
Thanks!
XTutorials said:
I instaled persona78's B600 mod on TWRP 3.0.2-0 and rebooted. Just boot logo. Nothing else. No recovery, no fastboot, nothing. After struggling a bit I mamaged to get into fastboot, but when I run adb command in Windows 8.1 it says "waiting for device" and that's it. I tried several tools and "kits" with more functions, one of them being TWRP.
Please help! Tommorow morning I have a working trip and I extremely need my phone, and in my country it's already 1:00 a.m.
I will be very thankful for any solution and fast response.
Thanks!
Click to expand...
Click to collapse
Try flashing it again and yes..
....B600 stays in boot logo for longer
HaiderHady said:
Try flashing it again and yes..
....B600 stays in boot logo for longer
Click to expand...
Click to collapse
I cannot acces NOTHING just fastboot. How I'm going to flash the rom again?
Linux saves phones, that is what I have to say.
Ran adb in windows: <waiting for device>
Ran adb in ubuntu: Revived my phone!
Thank god this phone is fixed, otherwise I couldn't continue my developing on PA
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command
fastboot devices
Click to expand...
Click to collapse
should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all ALE-L21 firmware. Find the latest. The latest FULL firmware for Europe region is C432B602 (Dual SIM) and C432B603 (Single SIM). Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
That last one may take a bit. Then you can do
fastboot reboot
Click to expand...
Click to collapse
JpegXguy said:
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all Huawei firmware. Search (F3 or Ctrl+F) for ALE-L21 and find the latest firmware. (For example, if you search ALE-L21C432 the latest firmware is B600 as of the time of writing this) Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files.
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
That last one may take a bit. Then you can do
Click to expand...
Click to collapse
Thanks for the help. But I already fixed my problem.
XTutorials said:
Thanks for the help. But I already fixed my problem.
Click to expand...
Click to collapse
Just in case someone stumbles upon this. I hate when the forum ends abruptly
JpegXguy said:
If you are truly in fastboot mode, with the green android dude (his name is Andy) and the white background then the command should return your device's serial number. Then you can go ahead and flash the 4 needed partions from the stock ROM with fastboot.
First of all, you need the 4 .img files for boot, recovery, cust and system.
You can get these as follows:
On this page you can find all ALE-L21 firmware. Find the latest. The latest FULL firmware for Europe region is C432B602 (Dual SIM) and C432B603 (Single SIM). Download the FULL version (not OTA) and use Huawei Update Extractor to extract boot, recovery, cust, and system as .img files
Open a command window in the folder with the files and rename them accodingly if you wish (e.g. 06.boot.img -> boot.img)
Then you can flash them in fastboot mode like this:
That last one may take a bit. Then you can do
Click to expand...
Click to collapse
it say partition length error please help