Database Info

[Q] Bricked from rom manager :(

So I figured that since I've used rom manager before on other devices and had no issues that I would just flash clockworkmod via the app. WRONG. Now I'm bricked with no access to adb and presumably no access to fastboot (my TF doesn't show up under fastboot devices). My computer still recognizes the tablet as a media device or something though, evidenced by the "bloop" noise when I turn it on while connected to my PC.
I am however able to access the recovery kernel (the android lying on its back with the chest open and a warning symbol above it?). I was wondering if there was ANY way at all to reflash with a proper CWM or simply revert to stock or something? Honestly I have no qualms with cracking open the device and manually accessing and editing the filesystem from its hard-drive (if that's even possible...)
Failing this, is there any way to convince Asus to replace my tablet for me? I've already gone through the root process, so it's unlocked and I assume that means there's no way to get the warranty back. I'm open to any suggestions that will make my tablet more than just a $400 hunk of plastic. I will definitely be sending the dev team for rom manager all of my annoyance... but any and all replies are appreciated...
*edit* maybe not so bricked after all?
I was able to send the recovery.img from http://forum.xda-developers.com/showthread.php?t=1668173 to the device and presumably flash it to the device...
C:\Fastboot>fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)... OKAY [ 2.424s]
writing 'recovery'... OKAY [ 2.069s]
finished. total time: 4.493s
Click to expand...
Click to collapse
I also was able to reboot the device from fastboot, so I suppose fastboot works. I think this means I can save it? I guess I'll keep looking, but I'm still not quite sure...
edit2* Yay! Able to access CWM because of the previous link! Now to see if I can flash one of the official ICS roms...
edit3* K, well I don't have a microSD converter on hand, but every attempt to flash or boot via fastboot has failed, IDK why. I guess if I figure it out tomorrow by putting update.zip on the SD and flashing via clockworkmod, I'll post it...

power off
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks

I am in the same boat. What I did is a CWM backup, then loaded the Cyanogen mod. Decided to go back to my backup so I went to CWM Recovery. Seemed to load everything just fine but when it reboots it is just a black screen......I also cannot see the sd card in CWM and cannot access Fastboot because the MTP driver will not install (maybe because of Cyanogen)........still working on it. Pass along anything you can think of.....I will try anything at this point.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
abe_cedar said:
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks
Click to expand...
Click to collapse
Probably becasue your MTP drivers are not installed. I am having the same issues, but windows will not install the MTP driver......

Did you try to restore the recovery from rom manager? Or all you did was back it up? I ask because I too backed up recovery from rom manager but my tf300 is fine. I no now not to restore the back up.
If you did restore from rom manager. Why?

MTP
My drivers I believe are fine. I was able to adb flash the CWM before I did flash from the CWM app the wrong one. Xplodwild was saying that with the wrong CWM on the tab ( I have now the tf201 version on ) no one was able to recover. I guess I am stuck.

abe_cedar said:
Were you able to power the tab off and the power it up using power+ vol down?
I can't get into the usb debugging mode. The CWM cannot see ( tried to mount it) the SD.
Thanks
Click to expand...
Click to collapse
Hmmm... I can make it reboot by holding down the power button, then get into the recovery settings via the volume buttons. All that's really stuck is the bootup stuff. Although half the time fastboot recognizes it and half the time it doesn't... CWM doesn't recognize my SD either, just shows me a CWM folder.

trevor7428 said:
Did you try to restore the recovery from rom manager? Or all you did was back it up? I ask because I too backed up recovery from rom manager but my tf300 is fine. I no now not to restore the back up.
If you did restore from rom manager. Why?
Click to expand...
Click to collapse
All I did from rom manager was flash CWM. I didn't restore anything or backup anything... I should have backed it up though... Anyways, CWM works fine, so I don't think that's the problem at this point. I wish I understood more about the Android operating system, cuz I'm not sure what exactly I can blame at this point...
I flashed the Team Win Recovery Project kernel, which seems to work pretty well... it allows me to see that... there's an SD CARD partition on my main drive? wtf? lol. Anyways, it doesn't have external storage support, so that option is out. But it means that I'm able to flash things still... maybe I just need the right system file? I'll keep trying.

To push files in recovery try installing the drivers from my thread: http://forum.xda-developers.com/showthread.php?t=1680570
Recovery doesnt support external SD so this should work for you.

Northern-Loop said:
To push files in recovery try installing the drivers from my thread: http://forum.xda-developers.com/showthread.php?t=1680570
Recovery doesnt support external SD so this should work for you.
Click to expand...
Click to collapse
Hmmm... it does show up in adb devices, however I'm unable to push this way. This is what I'm seeing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I very well may be doing something wrong, but I don't know what... This is the closest I've been so far though

BlakeC90 said:
Hmmm... it does show up in adb devices, however I'm unable to push this way. This is what I'm seeing:
[IM]http://screensnapr.com/e/IJ4Zru.png[/IMG]
I very well may be doing something wrong, but I don't know what... This is the closest I've been so far though
Click to expand...
Click to collapse
Error seems to relate to "USB Debugging Mode" I guess you didn't enable this before the brick happened?
Try "adb shell" then su
Well reading more debugging is switched on in recovery.

Northern-Loop said:
Error seems to relate to "USB Debugging Mode" I guess you didn't enable this before the brick happened?
Try "adb shell" then su
Well reading more debugging is switched on in recovery.
Click to expand...
Click to collapse
USB Debugging WAS enabled when I started all this debauchery, but I've cleared so many things and reflashed stuff so many times it very well could have reset itself or something. I'll try what you suggested though and post the results. Thanks for the suggestions, btw

Not sure it will make any difference but try putting the path in quotes
ie
adb push "c:\romfolder\roms.zip" \sdcard\ROMs
SU command wont work, doesnt work on my tab.

Northern-Loop said:
Not sure it will make any difference but try putting the path in quotes
ie
adb push "c:\romfolder\roms.zip" \sdcard\ROMs
Click to expand...
Click to collapse
using adb shell > su doesn't appear to work for me, perhaps because of it being set up in recovery?
I have little experience with adb in general, let alone adb shell, so once again I could be doing it wrong. But I don't think so...
Using quotes, however, it's taking a lot longer to run the line... I hope that means it's working XD
edit* Hmmm... can't tell if it worked or not. It won't show in recovery, but this is what showed in cmd:

BlakeC90 said:
using adb shell > su doesn't appear to work for me, perhaps because of it being set up in recovery?
[IG]http://screensnapr.com/e/A96dAy.png[/IMG]
I have little experience with adb in general, let alone adb shell, so once again I could be doing it wrong. But I don't think so...
Using quotes, however, it's taking a lot longer to run the line... I hope that means it's working XD
Click to expand...
Click to collapse
Yes it should return file sent now

Northern-Loop said:
Yes it should return file sent now
Click to expand...
Click to collapse
*sigh* it worked once, but after that just more protocol errors. I don't know if it technically worked because it doesn't show in recovery and it didn't say file sent.
...I have an option to wipe the system... that would screw things up as badly as I imagine, correct? I think I want to shy away from that, but it's the one thing in recovery I haven't tried...

Try unplugging USB cable or rebooting into recovery?
Protocol error seems to be generic error
Sent from my GT-I9100 using xda premium

Northern-Loop said:
Try unplugging USB cable or rebooting into recovery?
Protocol error seems to be generic error
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Continues to do the same thing... protocol failure... I keep messing around, but honestly I'm confused as to why it won't work... I mean what could the possible reasons be?
I've also tried flashing through fastboot, to no avail.
YESYESYES! I don't know why it decided to work this time, but for some reason, I got it! Fastboot saved me, somehow...

Great news - Has it booted now?
If so I will update my ADB/Bricked Recovery thread with the details on how to recovery from TF201 Recovery Firmware?

Northern-Loop said:
Great news - Has it booted now?
If so I will update my ADB/Bricked Recovery thread with the details on how to recovery from TF201 Recovery Firmware?
Click to expand...
Click to collapse
It's up and running fine! As far as I know, all that should be necessary is the fastboot stuff, so long as you're able to access it... If not, then I think you're SOL... I guess just flash the .29 update blob and it will work? XD I'd try it again and make sure, but I don't have the balls. I guess just tell people to try that though, and if it works, it works. Thanks so much for your help!

BlakeC90 said:
It's up and running fine! As far as I know, all that should be necessary is the fastboot stuff, so long as you're able to access it... If not, then I think you're SOL... I guess just flash the .29 update blob and it will work? XD I'd try it again and make sure, but I don't have the balls. I guess just tell people to try that though, and if it works, it works. Thanks so much for your help!
Click to expand...
Click to collapse
Thanks I'll add credit to you for being the unlucky/though lucky for getting recovery back. As we have a separate recovery I always thought it would of been possible to recovery if you flash bad rom or bad recovery.
Can you vet the info I have put into my thread http://forum.xda-developers.com/showthread.php?p=26724020#post26724020
Installed drivers, boot into to fastboot to flash recovery then fast boot system blob file?

Well I screwed up

Okay, so SOMEHOW I downloaded the crespo factory images and flashed the bootloader and then the radio. The system update wouldn't flash and this is when I realized my horrible mistake. So I downloaded the correct factory images. But now, I have no USB access on the thing. Can't fastboot. Can't adb. Phone boots and charges over usb. I can reboot into the bootloader, but my computer doesn't recognize the phone is even attached. I can reboot into recovery (I still have CWM on there) but what can I do from there? Am I TOTALLY ****ed? Please please please help!.....

I think what I need is a CWM flashable bootloader zip file. Or a complete OTA ROM Update zip file that flashes ROM, radio, and bootloader. Since I have CWM I think either of these will work for me, but I can 't find anything like this for the Nexus S 4G. Can anyone help?

have you checked if your computer recognizes your phone on odin mode? if it does you can prob try this
http://forum.xda-developers.com/showthread.php?t=1575502

JOEOZUNA4U said:
have you checked if your computer recognizes your phone on odin mode? if it does you can prob try this
http://forum.xda-developers.com/showthread.php?t=1575502
Click to expand...
Click to collapse
Unfortunately it doesn't. My computer doesn't recognize this phone at all anymore, not in fastboot or download mode, or even just booted into Android. If someone could PLEASE show me where a CWM flashable file that will flash the bootloader is, or make me one, I'd pay some good $$$ for it. Please help?

You flashed the bootloader & radio with ODIN?

supercluver said:
Unfortunately it doesn't. My computer doesn't recognize this phone at all anymore, not in fastboot or download mode, or even just booted into Android. If someone could PLEASE show me where a CWM flashable file that will flash the bootloader is, or make me one, I'd pay some good $$$ for it. Please help?
Click to expand...
Click to collapse
Give me a sec I will try to make a flashable CWM with just the bootloader. No need for donations

polobunny said:
You flashed the bootloader & radio with ODIN?
Click to expand...
Click to collapse
I flashed the CRESPO bootloader and radio via fastboot. Then when I tried to flash the ROM update via fastboot it gave me an error. This is when I noticed I was using the CRESPO files instead of the CRESPO 4G files.... Now, after rebooting, my computer WILL NOT recognize the phone at all via usb, in any way, fastboot, ODIN, nothing. But otherwise the phone seems fine. It charges over USB. It boots and I can get into recovery (and I still have CWM) so if I could download a file over wifi (which I can, already tried) and then flash said file via CWM that would flash the new bootloader, I'd be good to go.

rasengan82 said:
Give me a sec I will try to make a flashable CWM with just the bootloader. No need for donations
Click to expand...
Click to collapse
Dude THANK YOU.

I don't think that's possible though, to make a CWM flashable bootloader. :|

Here ya go man. Hope this helps.
https://www.dropbox.com/s/0yemj2aybmdda4f/crespo4g_bootloader_rasengan82.zip

polobunny said:
I don't think that's possible though, to make a CWM flashable bootloader. :|
Click to expand...
Click to collapse
I'm pretty sure it is, as a complete OTA zip will flash the radio, bootload, and ROM, at least I think it will....

rasengan82 said:
Here ya go man. Hope this helps.
https://www.dropbox.com/s/0yemj2aybmdda4f/crespo4g_bootloader_rasengan82.zip
Click to expand...
Click to collapse
Here. Just in case you missed from previous page.

rasengan82 said:
Here. Just in case you missed from previous page.
Click to expand...
Click to collapse
THANK YOU! Worked perfectly. Flashed, rebooted to bootloader, and computer recognized the device again. You are a life saver! You sure no donations are necessary???

supercluver said:
THANK YOU! Worked perfectly. Flashed, rebooted to bootloader, and computer recognized the device again. You are a life saver! You sure no donations are necessary???
Click to expand...
Click to collapse
Nah it's alright man. Glad it worked!

NVM RAS is da man!
Can you put the phone into download mode?
1. Unplug USB and pull the battery. then replace the battery.
2. with the volume up and vol down buttons held down. Press and release the power button for about a sec.
If you get the same as the picture below follow the procedure found here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i flashed a CM nightly build.. which is out nof the norm for me kuz i usually stick with #euroskank and i lost all USB capabilities too. everything else works perfectly, charges fine and all..
i flashed the above zip and it gives me temp access via USB but if my phone goes to sleep or if i reboot im back to square 1 and have to re flash... dunno wtf i did but damn this sucks

kalico17 said:
i flashed a CM nightly build.. which is out nof the norm for me kuz i usually stick with #euroskank and i lost all USB capabilities too. everything else works perfectly, charges fine and all..
i flashed the above zip and it gives me temp access via USB but if my phone goes to sleep or if i reboot im back to square 1 and have to re flash... dunno wtf i did but damn this sucks
Click to expand...
Click to collapse
Did you ever get this resolved? I did something VERY similar when I first started modding on this phone, and experienced VERY similar issues. I have an AWESOME fix, even though it leaves the download screen looking like the oem unlock screen if you put oem lock back on (otherwise it looks normal, and who the heck would do that is beyond me - I only found it when I originally took it back to COMPLETE stock), but it functions fine, and this will take you back to gb, but it seems like the 'fixall' for this phone, and you can always reroot, reflash cwm via fastboot, etc, after using it.
Let me know.
Peace..
~WickiD~

DONT POST IN THE DEVELOPMENT THREAD UNLESS YOU'RE RELEASING A ROM KERNEL OR RECOVERYY!!!
this needs to be moved to Q&A or General...
BIGGEST PET PEEVE!!!!!!!!!

[Q] Is it bricked or hardware?

Hey.
So i bought a tf101 and it was never rooted before if you believe the previous owner. I used easyflasher to install, then installed cm10.
So yesterday i was going to bed, open the tablet and boff. Just died.
I could enter the APX mode (i saw it popped up when i connected it to the computer) but nothing else. So since it was late i thought i'l do the unbrick with easyflasher today.
Now i can't even enter APX mode.
So how do i know if it's bricked or hardware issues? Cause i've got ½ year of guarantee left on it.
EDIT: I can now enter APX mode for some reason, tried the unbrick on easyflash. Im using the WW SKU version. The easyflasher seems to have trouble cause the "wheele.exe" get's closed everytime after it uploaded the bootloader to 100%. But the installation still says it's done and no other errors shows up. But still not able to boot anything on the device.

One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?

Lethe6 said:
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Click to expand...
Click to collapse
This is just wierd. Now it will boot, but only if it's in the charger... When i plug it out it dies. The battery says 76% and haven't moved so the battery seems dead?
And i've got the b50.
This is how it looks when i use easyflasher when it's on APX mode (as it was when i flashed recovery with easyflash). But when i boot up the tablet with charger it's still cw10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.

Lethe6 said:
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Click to expand...
Click to collapse
I've installed the drivers as wanted by EF. I can browse the internal SD without any problems so i'm not sure about that. Anyway to test that?
I think im gonna download some other rom right to the tablet and try install it. Otherwise i have to go and buy a sd-card thingy for the computer so i can try install stock rom that way i guess.
edIt: Installed Team EOS 4 *JELLYBEAN MR1* but diden't make any diffrence. Now i just need to try get stock and un-root so i can send it to asus :/

So i kinda got it to work out. I think.
I could keep the tablet alive after a while using the keyboard dock after having it being charged for about 10 min. So i had do unistall the "normal" drivers which i could not accsess before and then i worked to make normal rom with easyflash.
But question is:
Is the WW SKU right one for me (im from sweden.)?
Does the recovery go back to orignal also? When i tried to accses recovery all i got was the android green guy who had something wrong with his stomach. Means im back to orginial recovery?
Cause im gonna go back to the store as warranty issue, but i'd like to make it looked as much as possible that it was never rooted or had diffrent roms the the orgiinal.

Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.

Lethe6 said:
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Click to expand...
Click to collapse
I downloaded some "check if rooted" app an it says it was not properly rooted which i guess means there is no root existing. Ty for your help man, been awsome. Just hope i won't get charged by asus somehow

Yeah hope so too! Let us know how it ends up going

Worse comes to worse, use PERI http://forum.xda-developers.com/showthread.php?t=1681155
Sent from my Transformer using Tapatalk HD

Lethe6 said:
Yeah hope so too! Let us know how it ends up going
Click to expand...
Click to collapse
So, just wanna update the thread.
The battery was dead so switched it myself after buying one for 50-60 dollars on ebay. Was quite easy, only painful part was putting on the thing around the screen with the power button etc so it would work.

Sweet, glad you got it fixed

[Q] help! think i bricked my tf700

help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S

prasse said:
help im in trouble, i went from parandroid rom to do a nandroid recovery to clean rom and now my dear tf700 wont boot up i get the asus loading screen and thats it, i cant go into recovery either....what i can do is get into an option screen that i havent seen before where i can wipe ( dosen´t help) or connect with usb, but that dosent do anything... please help im getting desperate here :S
Click to expand...
Click to collapse
How long did you let it sit on the Asus screen?
Which recovery and version?
I've seen my tablet take 45 minutes to boot on older versions of TWRP after a ROM flash.
This hasn't happened for quite a while however.

This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?

sbdags said:
This is really important - which version of the bootloader are you on and which version of which recovery do you have installed?
Click to expand...
Click to collapse
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s

prasse said:
Ye gave it a couple of hours The first time, and The custom recovery is twrp of goomannager so gotta be one of The newer version, can't rememeber The excat version however :s
Click to expand...
Click to collapse
Do yo usee ANY number flying about giving any indication as to what bootloader you're on? sbdags made an important point -- you'll need a current bootloader version to get the more recent ROMs working.
Oh, and ehh... please use interpunction -- you know, periods and commas and stuff. It makes a sentence that much more readable and understandable.

okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:

prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?

sbdags said:
When you reboot with power and volume down it tells you the bootloader version in the top left. What is it?
Click to expand...
Click to collapse
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.

prasse said:
thats just the thing, i don´t get the normal bootloader, instead i get a messeage saying " os will cold boot in 10 secs" and option to either wipe data or start fastboot usb download protocol"
but the last option doesen´t really do anything.
Click to expand...
Click to collapse
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.

sbdags said:
Sounds like you are on the ICS bootloader which means you have probably bricked your tablet unfortunately.
Click to expand...
Click to collapse
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?

prasse said:
the jellybean 4.1 was official if i remember correctly, however the "upgrade" to 4.2 was through the parandroid rom. But how would i have updatede my bootloader then?
Click to expand...
Click to collapse
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?

prasse said:
okay im on twrp 2.4.0.1.... but i can´t enter the recovery mode :crying:
Click to expand...
Click to collapse
How do you know you're on TWRP if you can't get into recovery?

sbdags said:
The old ICS bootloader used to give some text first when booting with volume down and then you hit volume up to get some options.
The new JB bootloader gives 4 icons when booting with volume down held. It also tells you the bootloader version
From what you described it sounds like the old ICS bootloader. But of course I could be completely wrong as I can't see your screen.
Without you giving versions it is impossible to say what you have done but if you have done a reset from the bootloader (you said you have) and you are on the wrong recovery then you have likely bricked your device. Usually it was done with JB bootloader and an older version of TWRP. As you have said you were on 2.4.1.0(??) I'm not sure as you haven't detailed your bootloader.
Do you still have fastboot available? I.e., when you select it does it say starting fastboot?
Click to expand...
Click to collapse
okay thank you for the explanation, but no i dont have fastboot avaliable.... got the same screen as before.

ngionla appearance
Thats OK said:
How do you know you're on TWRP if you can't get into recovery?
Click to expand...
Click to collapse
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.

prasse said:
well i got those previously two mentioned options.....if i take the wipe option, it automatiaclly enters the custom recovery and starts wiping, however im not in control, and can´t do anything while it wipes.
Click to expand...
Click to collapse
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it anything like the above image?

Thats OK said:
Is there any way you could in some way put up a picture of the screen on the tablet?
When you mention "wiping" is that a system wipe or do you know if it is the eMMC (sd0) wipe?
Wish there was a way to see your tabs boot\recovery screen.
Is it anything like the above image?
Click to expand...
Click to collapse
Ye almost the excat same, i Can upload a picture when i get home... But no i dont know the difference between, your mentioned wipes sorry :s..

If it looks like that what happens when you push volume up on the RCK icon?

sbdags said:
If it looks like that what happens when you push volume up on the RCK icon?
Click to expand...
Click to collapse
see thats the difference, i only got the two last icons wipe and usb : /

That sounds like you do not have any recovery available. If you connect the tablet to the computer via SUB and pick the USB option, what happens?

Isn't the fastboot built into the bootloader? It should be always possible to recover if you can get to the recovery select screen and select fastboot, shouldn't it?

I Need Help to Recover my Phone Please

Hello,
I'd like to say I was told about this site, and I hope someone can help. I find the forum very difficult to navigate.
I have a moto G 2015 that I tried to root, but I fear that I made some mistake or downloaded a bad rom or something because I can only access the root loader, or w/e it's called. The new rom or recovery image or w/e (yes i'm sorry i don't know all the terms) never loaded, and even the backup (which installed successfully) won't load.
Can I factory reset my phone with the original android rom? I really like this phone and it's just a brick now. I'm using my old phone which i don't like as much. I hope someone can help.

You'll have to flash the stock firmware using fastboot, here is the guide. Refer first 2-3 posts by lost101 for the instructions.
Also, the guide has a link for the firmware index where you can download the latest firmware for your particular model (mine is XT1550, for example).
You should already have ADB and fastboot set-up on your PC as you have tried to root. Assuming that you're using Windows, Extract the firmware into the folder where adb.exe and fastboot.exe are located.
Now, boot the phone into bootloader mode by pressing and holding power+volume down button for about 7-10 seconds. You can release the keys once you see an Android robot lying on its back. The screen should read 'fastboot mode'. Connect the phone to your PC, the screen should now day 'USB connected'. Now open a command prompt from the location where you placed the firmware files. You're now ready to flash the stock firmware.
Follow the guide linked above for the required commands. Make sure to do the recovery flash first, factory reset, then reboot to bootloader again to continue rest of the procedure.
BTW, what was the backup you mentioned that restored successfully? Can you describe it more?
Broadcasted from Zeta Reticuli

Let me provide some images I took with my other phone. It might help.
OK I have osprey xt1540 and i used something called Team Win Recovery Project v2.8.7.0. I can still get into the TWRP thing, and there's a bunch of options i'm sure you're aware of. The backup of my phone that I made doesn't seem to work. It will load say that it loaded properly. Maybe I can provide some photos to show you what I've done.
The backup was simply a backup of my phone before attempting to flash it the first time. It was meant as a way to recover the phone I think..
edit: OK so I'm not allowed to post pictures because I have fewer than 10 posts. That's going to make it harder to get help.
edit 2: BTW In the list for stock firmware I'm not sure which one to take. I found the version of my phone, but it seems newer than any of those listed. 24.71.2 where the newest there is 24.65.33 ?
I found a more recent firmware, but it still doesn't exactly match my phone (I think?) I'll post them
My phone: 24.72.2.osprey_retca.retca.en.ca
Most recent found: MotoG3_XT1540_OSPREY_RETCA_5.1.1_LPI23.72-16.3_cid14_subsidy-DEFAULT_CFC.xml.zip
And I found it from this thread: https://forum.xda-developers.com/showthread.php?t=2537119
Also I wonder if my phone will work if I can just relock the bootloader somehow. I get stuck on that screen that warns about the bootloader unlocked (white screen with motorola warning.) I can get on that screen, the bootloader, and then the team win recovery thing. I hope this helps

First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.

KrisM22 said:
First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.
Click to expand...
Click to collapse
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.

mobile.frank said:
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.
Click to expand...
Click to collapse
I would need to see a copy of your terminal output.

Try what you were doing again in TWRP, this time after the error, use the third button on nav bar (right to the home button, 4 horizontal lines) to switch to terminal output window; then press and hold down power+volume down to take a screenshot and then upload it here, it might help us understand the situation better.
And if you are aiming for a stock firmware install, probably 'XT1540_OSPREY_RETCA_6.0_MPI24.65-33.1-2-2_cid14' is what you want. Got from the firmware index thread here.
BTW, you can try some threads on the off-topic section to increase your post count.
Broadcasted from Zeta Reticuli

KrisM22 said:
I would need to see a copy of your terminal output.
Click to expand...
Click to collapse
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything.) I imagine i have to update the TWRP from this screen, but the instructions in the links you sent me don't correspond with the files that I downloaded. If I type in what I downloaded it doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the program and screen and instructions. The codes there don't work because the filenames are different:
This is an example trying to use the recovery img which tbh I'm not even sure what image that is.
I attempted to root my motorola a long time ago, that's why i can't remember how i managed to do any of it. I think I deleted all the links to the instructions I was using.

mobile.frank said:
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything)
This is the program and screen and instructions. The codes there don't work because the filenames are different:
Click to expand...
Click to collapse
fastboot devices shows the devices that are in fastboot mode (same as bootloader mode in our case) connected to the PC. So, connect the phone via USB and try running that command, it'll show up your device's serial no. and 'fastboot' written on the right side.
Now, rename your recovery image to twrp.img. Or you n modify the command itself. Make sure that the recovery is in the same folder as these 4 files. For example, if your recovery is named twrp-3.1.0.0-osprey.img, then type in-
Code:
fastboot flash recovery twrp-3.1.0.0-osprey.img
after you get a [DONE], scroll down and select recovery in phone.
If you already have a twrp version installed now, then copy the new twrp.img file to your sdcard. In TWRP>Install>install image. Select the file, select recovery in next step and swipe to flash.
Broadcasted from Zeta Reticuli

from the lying down android in the first picture, it shows you have stock recovery.

KrisM22 said:
from the lying down android in the first picture, it shows you have stock recovery.
Click to expand...
Click to collapse
That's the bootloader screen, not recovery.
Sent from my MotoG3 using Tapatalk

OK I managed to update the TWRP and am trying to restore the phone backup from the SD card. I made the backup before making any changes when I tried to root my phone.
I don't know if anything works because every time the phone reboots I get the "Warning bootloader unlocked" screen; so maybe it even worked when i tried to root it, but is just always stuck on this screen. I only get that screen, or the bootloader screen if I go to it.
OK so I tried to follow these directions with the factory image for my phone, and it didn't work. I get a nice motorola boot screen, and then nothing:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#

I strongly suggest you look at this:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
That will also tell you how to get rid of the nasty bootloader screen.
Also make sure you WIPE dalvik/art,data,system,cache before you restore. Anything.