Related
Hello everybody
It seems I'm quite late with this issue so I wasn't sure whether to post in an old thread or open a new one...
A few days ago my 12-year-old nephew, for 3 month a really proud owner of a Nexus S I9023 came to me desperately sad: He had tried to update to ICS (the manual "update.zip method") and ended up with a totally unresponsive phone like many others back in December.
I do not own an Android device myself and this stuff is all new to me (so sorry for any dumb questions or thoughts ;-) ), but after some googling and finding this great forum and especially AdamOutler's tool (and reading about other people's success with it) I was confident to be able to bring the Nexus back to life. But I'm still stuck at a certain point...
What I've done so far:
-I installed Ubuntu 10.04.3 LTS natively on a PC (I failed with using a virtual installation on my Mac).
-Installed JavaSDK and the UnBrickable Resurrector.
-Downloaded the Android SDK from here and installed it following this advice (I didn't download fastboot separately as it was included in the SDK).
-Downloaded a full ROM from here , extracted the bootloader.img and boot.img from the .zip, downloaded recovery-clockwork-5.0.2.0-crespo.img and put all that stuff in the fastboot directory.
Ok, ready to go now (I think):
I start the Resurrector (R40), select "Nexus S", remove the battery, plug in USB, replace the battery (now the Resurrector recognizes the Nexus) and click "Perform Resurrection" (without holding any button on the Nexus). After a few seconds the Resurrector reports success, showing the "Android with speech bubble" and saying "Fastboot mode" below. On the Nexus the Search- and Homebutton (the both on the right side) are now lit-up, but the display is still black.
At this point I'm wondering if everything went ok, shouldn't the Nexus now already show its bootloader screen like on Adam's image or the battery charging screen ? Anyway, according to the Resurrector everything is fine, so let's continue.
I start Terminal and cd to the fastboot directory. Just to be sure the Nexus is recognized:
Code:
lsusb
Bus 002 Device 023: ID 18d1:4e20
Code:
fastboot devices
34329EB4B3F800EC fastboot
Now I'm not exactly sure what to do next. As far as I've understood some have now flashed the bootloader, boot & recovery images first, others have "booted from the recovery.img (?)", in both cases I end up with this:
Code:
fastboot flash bootloader bootloader.img
sending 'bootloader' (1536 KB)...
OKAY [ 1.629s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.631s
Code:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
downloading 'boot.img'...
OKAY [ 4.374s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 4.376s
But when I try to unlock, I only see this:
Code:
fastboot oem unlock
...
I wait several minutes but nothing happens. I stop this by unplugging the phone and an error appears:
Code:
FAILED (status read failed (No such device))
finished. total time: 561.710s
(I assume waiting nearly 10min is enough?)
I also tried to run fastboot as root with sudo, but that doesn't change anything. I'm really stranded at this point. :-(
This is my first contact with Android and I'm also not very familiar with Linux, but in my humble understanding I should be just one little step away from success, shouldn't I?
For me everything seems to work properly, the Resurrector reports success, saying the Nexus is in fastboot mode now, fastboot is running and recognizing it and also my attempts to "fastboot flash" or "fastboot boot" obviously work until the "Bootloader Locked" error pops up.
So the two big questions are:
1. Is it ok that after successful resurrection only Search and Home are lit-up, but the display remains black or should I see the bootloader or battery charging screen?
2. Why is fastboot stuck while unlocking?
I'm also wondering if it's worth it to set up a Linux/Windows dualboot installation to run fastboot or even Odin in Windows, I can't imagine that I have a better chance that way, this should work with Linux alone, shouldn't it?!
So, I hope I haven't bored you too much ;-)
I would really appreciate some help to make my nephew happy again...
Have a nice weekend!
If the bootloader is locked then you need to OEM unlock then on the screen it should say unlock bootloader? I need to press up with the volume keys and press ok power button.. Then it should be unlocked try that then white everything yo the phone
Sent from my Nexus S 4G using xda premium
In order to unlock oem, you first need to fastboot unlock which you did.
Then, confirm it on your phone which you didn't b/c you can't see/don't have fastboot screen.
And i think you didn't have fastboot screen b/c you didn't hold the buttons like you supposed to.
That's what everyone has to do to enter fastboot.
I think you should follow this thread.
And download and use the ROM package he has linked.
And instead of ODIN which requires Windows, you can use Heimdall which can run on Linux/Mac.
And search how to use Heimdall before flashing.
And if you don't have a backup, download some ROM (stock one preferred) to flash instead of restoring backup.
Also, search how to flash a ROM and clean/full wipe in CWM before flashing.
Same situation here, please help me.
Hello Cicofz and everybody,
I am stuck in about the same situation. Only a little later, my phone bricked on a 4.0.4 upgrade.
I used resurrection and on my phone the same Search and Home lit-up, the display remains black! but resurrection tells me it is in download or Fastboot mode. My fastboot on Mac doesn't get stuck, it tells me everything is Oke. However there is no possibility to get the screen on and really start fastboot on my phone...
So i think I'm stuck on the same thing you got stuck on some weeks ago.
Did you solve the problems in the meanwhile? If so can you please let me know how you did this.
If anybody els can help me please Do...
regards KnoefKnoef
Hello KnoefKnoef,
yes, I was able to bring the Nexus back to life (and a big grin back on my nephew's face) ;-) Afterwards it turned out pretty easy, just fastboot with Ubuntu, no need for any Windows stuff.
It's getting late here in Germany, so I'll try to recall and post what I've done tomorrow. I'm not sure, but I think I've even copied the whole terminal session so I can tell you step by step. I must have a look at the PC I used for it tomorrow...
Good Night
It is running... and yes it is on ICS 4.0.4.
thanks for your Quick reply, butt help is not needed anymore.
After using UnBrickable Resurrector in Linux I got the phone in download mode. with the home and search light glowing.
Then I Switched to Windows using this tread: *OFFICIAL* Android 4.0.4 IMM76D ROM for Nexus S 4G http://forum.xda-developers.com/showthread.php?t=1575502
It ended in a message Failed. Butt the phone was reboot-able. And best of all it is running on ICS 4.0.4.
So I'm very happy now.
It was quite a procedure doing all this on a MAC using Windows and Linux. Butt I eventually managed to do it....
Thanks for your input...
knoefknoef said:
thanks for your Quick reply, butt help is not needed anymore.
Click to expand...
Click to collapse
Pleased to hear that
Hi there!
I'm really hoping you guys can help me today. I tried installing the android 4.2 bootloader, following guide 2 in this thread (http://forum.xda-developers.com/showthread.php?t=2187982&highlight=android+4+2+1)
However, after following the instructions given, the rom wouldn't boot. I left it for about 15 minutes, before returning to flash touch recovery. However, this didn't work as you needed to boot into android before running it. I managed to get CWM Recovery installed on the tablet, however it caan't do anything as it just says "E: Can't mount /sdcard/". It says that on everything I try do (Obviously, the error's a little different each time, but it always starts with E: )
As I can still access fastboot, I'm hoping one of you can help me flash a new rom and get things back to normal.
Extra info:
I'm not amazing with this stuff, so please explain what you mean!
It's a TF300T, not the TF300TG
I have an SD Card if needs be.
Thanks for any help you give!
Sorry this isn't a pretty thread!
Apologies if I broke any rules, I've not really used the TF300T Forums, only the HTC Wildfire S ones!
you can try flashing the twrp 2.5 recovery. Make sure you flash the one for the 4.2.1 bootloader otherwise you will brick your tablet.
bloodyshyt said:
you can try flashing the twrp 2.5 recovery. Make sure you flash the one for the 4.2.1 bootloader otherwise you will brick your tablet.
Click to expand...
Click to collapse
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Unfortunately putting cwm on it means it is now bricked. Sorry
midgetman7782 said:
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Click to expand...
Click to collapse
You got twrp 2.5 to flash?
I am running openrecovery-twrp-2.6.0.0-tf300t-4.2.blob on 4.2.1 and having no issues.
Try it you have nothing to loose! Most people never get rid of cwm but it seems you did.
midgetman7782 said:
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Click to expand...
Click to collapse
Go home, splitscreen TWRP. You're drunk.
Go back to the TWRP thread and reread it again. It specifically says you'll need a particular version of the TF300T's firmware flashed before using TWRP 2.5.x, otherwise you'll have the dual display problem. To be safe, I'd flash the firmware (you can do it through fastboot) and then reflash TWRP. Worked fine for me, although I'm not touching it until more ROMs are safe with 4.2.
It lives!!!
Sorry I've been quiet over the past few days guys, I've been really busy with Sony.
Anyway, I thought I'd try to explain how I got my tablet working again...
Giving up hope, I left it just to bootloop, in hope it might somehow actually boot. I couldn't do anything else as CWM wouldn't do anything, and my tablet wasn't seen by my PC or ADB. After 45 minutes, windows 8 (8.1 to be exact ) made a noise to say that something had been connected, I jumped up (Knocking over my glass of water -_-) and sure enough, The USB devices saw something called "???????"
Obviously, this is a little thing, but I was filled with hope. I got into adb, and asked to see connected devices. It once again saw "???????" and I almost fell off my chair. I flashed the correct version of TWRP and then flashed myself a rom!
For some reason, at somepoint during the driver installation, the bootloader f*cked itself up. It became the 4.1 bootloader with 4 icons, but still said it was the 4.2 bootloader. I know it was the 4.1, because only roms for the 4.1 bootloader flash. I don't dare try flash it again though, as that's where problems arose last time, even if I'm pretty good at this whole rooting business
So long story short, I was informed I was in a hardbrick, that needed to have the motherboard replaced....and I still fixed it!
I think that as the tablet booted, connected to my PC, it installed the drivers to my PC that had been lost. So, If you're in this state, try that!
Hope this helped someone somewhere, it certainly helped me!
PS: Ever since the accident, my tablet's been INCREDIBLY laggy. Unlocking takes 5 seconds, home takes 5 seconds, app menu takes a bit longer. It lags on all menu's and so on. Any idea's why? I'm running the latest version of Paranoid Android. Oh, and the holo animation just dies.
Next time (if you still want to upgrade to 4.2 or downgrade, etc) please read carefully!!
i attempted it once (just for the lolz) i succeeded upgrading to 4.2 and downgrading back to 4.1
Sent from my TF300T using xda app-developers app
midgetman7782 said:
Sorry I've been quiet over the past few days guys, I've been really busy with Sony.
Anyway, I thought I'd try to explain how I got my tablet working again...
Giving up hope, I left it just to bootloop, in hope it might somehow actually boot. I couldn't do anything else as CWM wouldn't do anything, and my tablet wasn't seen by my PC or ADB. After 45 minutes, windows 8 (8.1 to be exact ) made a noise to say that something had been connected, I jumped up (Knocking over my glass of water -_-) and sure enough, The USB devices saw something called "???????"
Obviously, this is a little thing, but I was filled with hope. I got into adb, and asked to see connected devices. It once again saw "???????" and I almost fell off my chair. I flashed the correct version of TWRP and then flashed myself a rom!
For some reason, at somepoint during the driver installation, the bootloader f*cked itself up. It became the 4.1 bootloader with 4 icons, but still said it was the 4.2 bootloader. I know it was the 4.1, because only roms for the 4.1 bootloader flash. I don't dare try flash it again though, as that's where problems arose last time, even if I'm pretty good at this whole rooting business
So long story short, I was informed I was in a hardbrick, that needed to have the motherboard replaced....and I still fixed it!
I think that as the tablet booted, connected to my PC, it installed the drivers to my PC that had been lost. So, If you're in this state, try that!
Hope this helped someone somewhere, it certainly helped me!
PS: Ever since the accident, my tablet's been INCREDIBLY laggy. Unlocking takes 5 seconds, home takes 5 seconds, app menu takes a bit longer. It lags on all menu's and so on. Any idea's why? I'm running the latest version of Paranoid Android. Oh, and the holo animation just dies.
Click to expand...
Click to collapse
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
jaffer707 said:
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
Click to expand...
Click to collapse
Once my pc detect it on ADB mode i can slove it as well
jaffer707 said:
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
Once my pc detect it on ADB mode i can slove it as well
Click to expand...
Click to collapse
It was the animated one. Good luck dude!
midgetman7782 said:
It was the animated one. Good luck dude!
Click to expand...
Click to collapse
There's the difference. I don't even get that far. My tablet doesn't flash anything in fastboot, and I have no access to adb. My tab only boots to the splash screen and NO further.
______________________________
HTC Evo 4G LTE
midgetman7782 said:
Hi there!
I'm really hoping you guys can help me today. I tried installing the android 4.2 bootloader, following guide 2 in this thread (http://forum.xda-developers.com/showthread.php?t=2187982&highlight=android+4+2+1)
However, after following the instructions given, the rom wouldn't boot. I left it for about 15 minutes, before returning to flash touch recovery. However, this didn't work as you needed to boot into android before running it. I managed to get CWM Recovery installed on the tablet, however it caan't do anything as it just says "E: Can't mount /sdcard/". It says that on everything I try do (Obviously, the error's a little different each time, but it always starts with E: )
As I can still access fastboot, I'm hoping one of you can help me flash a new rom and get things back to normal.
Extra info:
I'm not amazing with this stuff, so please explain what you mean!
It's a TF300T, not the TF300TG
I have an SD Card if needs be.
Thanks for any help you give!
Sorry this isn't a pretty thread!
Apologies if I broke any rules, I've not really used the TF300T Forums, only the HTC Wildfire S ones!
Click to expand...
Click to collapse
here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
Now flash recovery.....
midgetman7782 said:
It was the animated one. Good luck dude!
Click to expand...
Click to collapse
That's not a hardbrick, 99% of the time that can be fixed. A Hardbrick is when it doesn't get past the bootloader.
Hi Folks,
The problem I am facing is, that, after i used the TWRP-formatting method, my TF700 won't get past the opening-screen of TWRP, instead, this screen continues to kind of blink in a 3 second rythm.
I installed the newest ZOMBI-POP, learned, that it didn't install the Google-Play-Services and the Gopple-Play-Store, reflashed it again and got massive lags (didn't check for the apps though) . I decided to wipe data and did this in twrp, using the command-line sbdag proposed, in the 'advanced' section. Somehow, I must have messed it up, because the 'blinkin' occured since then. I went into fastboot and tried to reinstall twrp 2.85, the result was the following:
C:\adb>fastboot devices
015d29955e53f60e fastboot
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7276 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.010s
Since then, the device 'blinks' as described and i even can't switch it off. Is there anything I can do? Searching the forum didnt give any results (maybe because of my minor knowledge) . I appreciate any help or tip, Thanks in advance!!
Tom
edit: Seems, that the problem was a not-working/installed adb-driver, i reinstalled it and fastboot flash worked. So, after two nights of try and error, it solved itself, finally when I overcame to get help here But trying to get into twrp still remains in that blinking with no step egtting further. Booting the system works.
frozentoes said:
But trying to get into twrp still remains in that blinking with no step egtting further. Booting the system works.
Click to expand...
Click to collapse
This means that TWRP crashes after starting, then it's restarted by init. Run "adb pull /tmp/recovery.log" and paste it.
Hello _that,
thank you for your reply. Alay, I did a step back, reflashed twrp with adp (2.8.5, i know, its not the recommended choice 'cause of the formatting-issue, but I will step around it) and flashed my B4-restore back. Since now, it works quite well in the behaviour that it showed before, a bit slow and a bit laggy, but working. I did this, because the device went hot and had a massive battery-drain, altough I installed the patch. Pretty sure, I messed something up while following the recommendations and tuts here, no one to blame but me! I appreciate the help I always find here by reading through the posts and I really appreciate the effort by every helper here - and yours and sbdags for the massive fun you put back in a tablet, that has been abandoned by its creators!! One issue I found with installing RC1 was, that it did not install gplaystore and gplayservices, was that left out or does it fall under rtfm?
Thanks
Tom
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
Download the toolkit and choose option to download and install the latest factory build and when it asks if you want to erase data type n (no) so you will not lose anything. Just make sure you are on the slot that was active which i believe u said was b
quangtran1 said:
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
Click to expand...
Click to collapse
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
llong31 said:
C:\Program Files (x86)\Minimal ADB and Fastboot
Click to expand...
Click to collapse
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Sounds like when I lost a recovery in one slot doing a sideload in TWRP. I did the temp TWRP load and then added TWRP properly from there. No issues after.
llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
I had to do the flash all once because I wiped the whole OS. I just ran it without specifying _a or _b and it worked like a charm. I think where to flash it is in the bat file so it puts it in the right place on its on. I didn't take out the -w to save my data.
TonikJDK said:
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Click to expand...
Click to collapse
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
GeekMcLeod said:
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
Click to expand...
Click to collapse
I am not so sure minimal even supports dual partitions. It's latest version is from April. Long before all of this. Might be why people are getting in trouble. It works if you don't specify partition sometimes it seems....We might be on to something here.
quangtran1 said:
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
Click to expand...
Click to collapse
Interest to know what you do? Can I have a job
aholeinthewor1d said:
Interest to know what you do? Can I have a job
Click to expand...
Click to collapse
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
aholeinthewor1d said:
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
Click to expand...
Click to collapse
Understandable.
quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
llong31 said:
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
There was absolutely no negative connotation in my comment. I stand by my experience that it is improbable to brick a smart phone. I'm just flabbergasted that it happens at all to anyone these days.
llong31 said:
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
TonikJDK said:
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
Click to expand...
Click to collapse
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Sure, a corrupt system would certainly cause the battery replenishment logic to misbehave. It won't know when to fast charge, when to maintain, when to trickle, etc.
llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Did you have an outdated fastboot binary? If you can still get in bootloader, I'd try with the good fastboot from the Android SDK.
So anywone with the newest G91 Max phone.
Device: Blu g91 max g0690ww
I couldn't find any info on rooting this since it's so new. So here is how I did it:
Here's the firmware link in case you wanted to patch the boot file yourself. But I'm including it already patched for convenience.
Blu_G91_Max_G0690WW_MT6785_V11.0.03.01_Generic_211222
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
**Your phone will be erased and warranty void**
Download Magisk patched boot file:
magisk_patched-24301_6WKnK.img - shared with FileRun
bananaspider.com
Place file in your fastboot folder.
Under Developer Options of phone, turn USB debugging ON, turn OEM unlocking ON.
Boot to Fastboot mode: hold volume up, down and power until phone screen turns off. Release power until text on screen. Use the up volume to select Fastboot mode and down volume to choose it.
Now that you are in fastboot mode, plug phone into computer and: (I'm using Linux)
Open command or terminal from your Fastboot folder:
[email protected]:~/Downloads/platform-tools$ fastboot devices
1010305022004085 fastboot
[email protected]:~/Downloads/platform-tools$ fastboot flashing unlock
(bootloader) Start unlock flow
OKAY [ 43.978s]
Finished. Total time: 43.978s
[email protected]:~/Downloads/platform-tools$ fastboot flash boot magisk_patched-24301_6WKnK.img
Sending 'boot_a' (32768 KB) OKAY [ 1.056s]
Writing 'boot_a' OKAY [ 0.081s]
Finished. Total time: 1.154s
[email protected]:~/Downloads/platform-tools$ fastboot reboot
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.204s
Once booted, Check Magisk for root.
**DEVS! Any ROM support here?
First of all, thank you! I was successful after following your instructions.
Unfortunately, my sim card is no longer being recognized. Did you have any issues with this?
Hey thanks a lot good to know it helps somebody. no issues with the SIM card so far. I'm using mint mobile SIM.
jasonbiggs said:
Hey thanks a lot good to know it helps somebody. no issues with the SIM card so far. I'm using mint mobile SIM.
Click to expand...
Click to collapse
I am using T-Mobile and it was working at first but then after I restarted the phone it stopped working. All the options for mobile network are grayed out. I tried factory resetting and doing everything over again with the same result. I also verified that it is not the SIM Card. I am at a loss here. I also re-locked the boot loader, which led to a boot loop but I was able to get the phone back into fastboot mode and fixed that. I'm going to try to flash the stock image and see if it helps.
Yes I flashed the stock image just to see if I could and it worked flawlessly maybe that'll help you out good luck.
jasonbiggs said:
Yes I flashed the stock image just to see if I could and it worked flawlessly maybe that'll help you out good luck.
Click to expand...
Click to collapse
Thank you. I didn't actually end up flashing the stock image yet, but I did do a factory reset again and then I left the house for about 30 mins and had left it on the setup screen at home. When I came back the sim card and mobile data were working, so perhaps it just needed some time to connect or what not.
z0ne_tripper said:
I am using T-Mobile and it was working at first but then after I restarted the phone it stopped working. All the options for mobile network are grayed out. I tried factory resetting and doing everything over again with the same result. I also verified that it is not the SIM Card. I am at a loss here. I also re-locked the boot loader, which led to a boot loop but I was able to get the phone back into fastboot mode and fixed that. I'm going to try to flash the stock image and see if it helps.
Click to expand...
Click to collapse
you probably aren't using the correct boot img. Did you use the one provided, or did you root it yourself?
dtingley11222 said:
you probably aren't using the correct boot img. Did you use the one provided, or did you root it yourself?
Click to expand...
Click to collapse
I used the one provided and after that I also patched one myself to see if there was a difference in the very beginning, but it was the same problem. All I had to do was wait about 30 mins and it worked just fine.
z0ne_tripper said:
I used the one provided and after that I also patched one myself to see if there was a difference in the very beginning, but it was the same problem. All I had to do was wait about 30 mins and it worked just fine.
Click to expand...
Click to collapse
oh ok cool
@jasonbiggs there probably is multiple gsis that are available for the phone. search phh gsi or andy yan gsi for lineage.
Any help with Blu S91 Pro? Can’t find firmware download anywhere.
Hey Jasonbiggs I have a BLU G91 MAX but in the developer optimazion when I first got it in the developer options they dynamic system updates so I installed when it said restart to finish installing my dynamic system update when it went to reboot the blu sigh came up but in small whit letters next to it say your phone's corrupted press power button within 5s to continue booting but then my auto rotate wouldn't work and a bunch of other features so I researched and sone1 said unlock the bootloader which I did with an OTG cable and 2 phones using the bugjaeger app and I have to leave my bootloader unlocked because if I close then alot of my apps won't work even tho i don't have a computer I disabled dynamic system updates but it still has the corrupt file and the only way to get rid of that is with a PC but since bootloader is unlocked I was just gonna root it with a better gaming ROM but idk how to that but sorry for the long message but I downloaded your page with the steps to the bootloader thing that is helping people so I was ted what do you think should cause I never closed my bootloader so please anything would be helpful