I recently saw many people running into this problem and didn't find any tutorial explaining how to fix it, so I decided make a little tutorial on how to fix this bug. Please understand that it only works on RSD Mode 3! And was tested only twice on an Everest Xoom and a Stingray Xoom (thanks droidxrooting)!
Click to expand...
Click to collapse
I'm not responsible if it Hard Brick your device! Everything you do is only your problem!
Click to expand...
Click to collapse
Windows:
Fully charge your Xoom
Download LordAIOTool
Extract it on C:/
Download and install Motorola Drivers
Download Motorola Stock ROM or any other ROM
Extract the ROM and pick the boot.img file
Copy the boot.img file to LAIOT bin folder
Now download any recovery (except Stock one) and copy it to LAIOT bin folder as well
Rename the recovery file to recovery.img
Plug your Xoom to your PC
Turn it on pressing vol- (If it worked the screen will stay stuck at Motorola logo with no text)
Open a cmd
Type:
Code:
cd C:/
cd LAIOT
cd bin
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Quickly press vol- (like after 2 seconds that Motorola logo appeared) and select Android Recovery
Now on recovery factory reset your device and wipe system
Flash a ROM
You're done
Click to expand...
Click to collapse
Linux:
Fully charge your Xoom
Download and install LordAIOTool
Download any ROM or Motorola Stock ROM
Extract from this ROM boot.img
Download a Recovery
Rename the recovery you just downloaded to recovery.img
Copy both boot.img and recovery.img to ~/LAIOT/
Turn on your Xoom while pressing vol- (if worked you will see a Motorola logo screen with no text)
Plug your Xoom to your PC
Open a terminal
Type:
Code:
cd ~/LAIOT/
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Quickly press vol- (like after 2 seconds that Motorola logo appeared) and select Android Recovery
Now on recovery factory reset your device and wipe system
Flash a ROM
You're done
Click to expand...
Click to collapse
Useful links
Motorola drivers (Windows): http://www.mymotocast.com/download/MDM?platform=windows
Stock ROMs: http://forum.xda-developers.com/showthread.php?t=1049485
Click to expand...
Click to collapse
The Windows version was tested on a Stingray (droidxrooting did it with my help) and the Linux version was tested on a Everest (XxLordxX did it)
Hope it unbrick your Xoom if it enters in RSD mode 3! I hope to soon add this feature on either LAIOT or/and 7Heavens Projekt.
Feel free to donate a little money for me due to the work I had writing this and studying on how to do it. I have a button called "Donate me" under my avatar, feel free to click it and make me happy
Re: [Tutorial]RSD Mode 3 "Brick" Fix
Thank you so much for your help. Yes I used Windows 8 and it worked like a charm. My only suggestion to improve this tutorial would be to link to the moto drivers and may be stock moto software.
Sent from my Xoom using XDA Premium App
droidxrooting said:
Thank you so much for your help. Yes I used Windows 8 and it worked like a charm. My only suggestion to improve this tutorial would be to link to the moto drivers and may be stock moto software.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Cool I will do it
Almost works, need guidance.
Hello XxLordxX
The 'Windows' hyperlink works, partially. When I click it, a new tab opens and the LAIOT.zip download starts.
Now here is the problem. It (LAIOT.zip) Will download all the way, and then it stead of giving me the file in my downloads folder, (and btw, I use Chrome) it says: 'Failed - Network error'.
I am stuck in RSD mode 3. But I can get to Fastboot doing the following:Rebooting (Volume up + Power) and then immediately press and hold Volume down as it boots, then giving me Fastboot.
Please help me. ANY help. My Xoom is MZ604.
Hi Mr_IceSlice,
The LAIOT is downloaded just because it contains some files that would make easier to user continue with commands, as it already contains adb and fastboot in some specific folders and such . If you can use fastboot, just skip to the 12th part and follow from there (don't forget to put the boot.img and recovery.img in fastboot folder).
Good luck
~Lord
Thanks! It worked. Need help with another issue.
XxLordxX said:
Hi Mr_IceSlice,
The LAIOT is downloaded just because it contains some files that would make easier to user continue with commands, as it already contains adb and fastboot in some specific folders and such . If you can use fastboot, just skip to the 12th part and follow from there (don't forget to put the boot.img and recovery.img in fastboot folder).
Good luck
~Lord
Click to expand...
Click to collapse
Thank you XxLordxX for your quick response!
I got my friend to download LAIOT.zip for me, and then send to me, so I was able to un-brick and get off the 'RSD mode 3' screen.
So, if I may ask, could you please help me with anther issue. I deleted my 'logo.bin' file from my device and need instruction on how to copy a logo.bin file onto my Xoom. The logo.bin file I have, I got from the SDK_tools, as well as one I got off of Google.
For for info on my predicament go to http://rootzwiki.com/topic/40350-ne...h-rooting-logbin-fastboot-and-adb-on-my-xoom/
To see the tutorial I was following go to http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
And yes, I do now realize that the tutorial is for HC, and I am on ICS. I started rooting about two days or so, before the JB update came out, so my Xoom still has ICS on it.
So to sum this all up, I think I have rooted my Xoom, using solarnz guide ( http://forum.xda-developers.com/showthread.php?t=1242241 ), but I cannot properly boot up and access my Android OS.
When I boot up, this is the screen I get https://mail-attachment.googleuserc...799&sads=7_VRHre5PhdRd_AciNMXSlUtgLM&sadssc=1
But by pressing Volume down to scroll/toggle to Android recorvery and then press Volume up to select, it will look like this: https://mail-attachment.googleuserc...370212413896&sads=ZvSKdQE0tH2Jz1gj-XJzHa-B_Nw
Then the screen goes black for a moment, then shows this: https://mail-attachment.googleuserc...370212419731&sads=VAE5PnZMIhbNT6ufO2D7g6Q5_xs
So, I know that I can unbrick my Xoom, I just someone to tell me what to do. Thank you again XxLordxX for helping me out! It feels good to know that there are still people out there who are kind enough to lend a helping hand. I can't wait to hear from you.
--Sincerely, Mr_IceSlice
Sorry but I can't see the pictures . Cna you upload to another server so I can view and help you with you problem . Sorry for the long time the answer took to arrive, I was busy with classes and studies lol.
Sent from my MZ608 using xda app-developers app
~Lord
Images attached for you.
XxLordxX said:
Sorry but I can't see the pictures . Cna you upload to another server so I can view and help you with you problem . Sorry for the long time the answer took to arrive, I was busy with classes and studies lol.
Sent from my MZ608 using xda app-developers app
~Lord
Click to expand...
Click to collapse
Here are the same images that I have attached the imagee as .jpg files.
In chronological order their file names are:
IMG_20130428_125548_440.jpg
IMG_20130602_172917_415.jpg
IMG_20130602_172924_314.jpg
And thanks allot for helping! I had to laugh when you said "Sorry for the long time the answer took to arrive, I was busy with classes and studies lol." because compared to the other forums/sites I've been on, your responses are lightning quick.
Hope the files/images work for you!
--Mr_IceSlice
P.S.
My Xoom does not have a SDcard, but my Mom's Droid RAZR MAXX does have a SDcard that I can eject and use with my Xoom to flash things with CWM.
Have you found any solutions yet?
XxLordxX said:
Sorry but I can't see the pictures . Cna you upload to another server so I can view and help you with you problem . Sorry for the long time the answer took to arrive, I was busy with classes and studies lol.
Sent from my MZ608 using xda app-developers app
~Lord
Click to expand...
Click to collapse
I haven't heard back from you. I was wondering if you have made any progress. Can you please give me an update?
Thanks a lot for your time and cooperation!
--Mr_IceSlice
@Mr_IceSlice Sorry, didn't have the time to look lol... I never saw that kind of error before, did you do something to your BL? It seems it was hacked or something like this . I will search a little and then try to give you an answer ^^
Sorry again,
~Lord
Not a glitch/hack. Noob error/brick.
XxLordxX said:
@Mr_IceSlice Sorry, didn't have the time to look lol... I never saw that kind of error before, did you do something to your BL? It seems it was hacked or something like this . I will search a little and then try to give you an answer ^^
Sorry again,
~Lord
Click to expand...
Click to collapse
In short it's not an error. It's simply because I erased the logo.bin file which contains boot animation.
So I don't have to repeat myself, please read and explore my post from 2nd June 2013, 05:42 PM. Thanks!
Also, I congratulate you for being faithful in trying to help me. Can't wait to hear from you soon!
--Mr_IceSlice
Mr_IceSlice said:
In short it's not an error. It's simply because I erased the logo.bin file which contains boot animation.
So I don't have to repeat myself, please read and explore my post from 2nd June 2013, 05:42 PM. Thanks!
Also, I congratulate you for being faithful in trying to help me. Can't wait to hear from you soon!
--Mr_IceSlice
Click to expand...
Click to collapse
I will try searching a little more on this, I'm somewhat very busy this week, so I will only be able to view better your issue at this weekend okay ? Just wanted to give you an up before ^^. Thanks for the patience .
~Lord
Sent from my Nexus 10 using Tapatalk HD
Okay! That will be great!
XxLordxX said:
I will try searching a little more on this, I'm somewhat very busy this week, so I will only be able to view better your issue at this weekend okay ? Just wanted to give you an up before ^^. Thanks for the patience .
~Lord
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That is totally cool with me. And I understand how life can get in the way, because I meant to reply to you yesterday, but I didn't get to it because I was still busy doing other stuff. Lol.
I'm a teen slightly younger than you. (I looked at your profile.) Thanks a lot again for responding in timely manner and helping me. I'll be looking forward to hear from you this weekend! You don't have to respond to this for me to know that you read it. Instead, go and spend the time you would have spent responding to me, and go do some research or chores or whatever, , or something productive! Lol. Thanks again.
--Mr_IceSlice
Are you still there?
XxLordxX said:
I will try searching a little more on this, I'm somewhat very busy this week, so I will only be able to view better your issue at this weekend okay ? Just wanted to give you an up before ^^. Thanks for the patience .
~Lord
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Hey, just checking in with you to see what progress you've made. I send you a $5 (USD) Paypal donation. The donation is sent from my mothers Paypal account, so it will have her name on it.
Hope to hear fro you soon.
-Mr_IceSlice
Mr_IceSlice said:
Hey, just checking in with you to see what progress you've made. I send you a $5 (USD) Paypal donation. The donation is sent from my mothers Paypal account, so it will have her name on it.
Hope to hear fro you soon.
-Mr_IceSlice
Click to expand...
Click to collapse
Thanks for the donation ! By the way, I got an idea now, I will try getting the logo.bin of my Xoom and sending to you! Then maybe you can push it via adb and seeing if it will work again . Good luck!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Woo hoo! Let's try it!
XxLordxX said:
Thanks for the donation ! By the way, I got an idea now, I will try getting the logo.bin of my Xoom and sending to you! Then maybe you can push it via adb and seeing if it will work again . Good luck!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
Ok! Sounds great!
You can send me the file as an attachment, or send it to me on Skype.
My Xoom has been hard bricked since February, so I am very, VERY, anxious/excited to try to get it fixed! Thank you so much!!!
-Mr_IceSlice
Can you send instructions?
XxLordxX said:
Thanks for the donation ! By the way, I got an idea now, I will try getting the logo.bin of my Xoom and sending to you! Then maybe you can push it via adb and seeing if it will work again . Good luck!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
If you can't get a copy of your logo.bin, just send me instructions on how to to put it on my Xoom, because I think I have a valid logo.bin file, it is not made for the Xoom but it will be functional which is essential. I am going on several trips soon, and having my Xoom is almost necessary. So please try to respond with info about how to get a new logo.bin file onto my Xoom.
Thank you for the help you have given.
-Mr_IceSlice
Please get back with me ASAP.
XxLordxX said:
Thanks for the donation ! By the way, I got an idea now, I will try getting the logo.bin of my Xoom and sending to you! Then maybe you can push it via adb and seeing if it will work again . Good luck!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
Please get back with me. It has been awhile and it would be nice to hear from you. If you could send some info about how execute the 'push' method, that would awesome.
But please get back with me soon.
-Best regards and hopes of hearing from you,
Mr_IceSlice
Mr_IceSlice said:
Please get back with me. It has been awhile and it would be nice to hear from you. If you could send some info about how execute the 'push' method, that would awesome.
But please get back with me soon.
-Best regards and hopes of hearing from you,
Mr_IceSlice
Click to expand...
Click to collapse
Hum... Sorry, I was heck busy currently! Too much things to be done xD. Anyway, I will tell you. Do the following, open a cmd and then copy the logo.bin to your adb folder. Then type the following :
Code:
adb push logo.bin /<insert the folder here>
adb shell "chmod 777 /<folder here>/logo.bin
Hope it helps... I will try getting a better tutorial as soon as I have some free time... Sorry again...
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Thanks for the quick reply, but...
XxLordxX said:
Hum... Sorry, I was heck busy currently! Too much things to be done xD. Anyway, I will tell you. Do the following, open a cmd and then copy the logo.bin to your adb folder. Then type the following :
Code:
adb push logo.bin /<insert the folder here>
adb shell "chmod 777 /<folder here>/logo.bin
Hope it helps... I will try getting a better tutorial as soon as I have some free time... Sorry again...
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
So I did what you said and it did not work. In cmd all I get (and this is for both lines of code you gave me) is:
Code:
error: device offline
I don't think you can whip up a reply this instant, but please tell me what you think/know about this error.
-Mr_IceSlice
Related
NOOBs or anybody struggling with this way of doing it listen up!!!!
I spent 24 hours trying these linux/mac/nightmare methods and had given up till i read this method http://www.machackpc.com/headline/how-to-r...android-os-2-1/
Worked first time and in less than 15 minutes i was done. So simple and you can do it all via windows with NO Virtual machine, no recovery menus or terminal instructions etc....
MAIN THING TO REMEMBER:
Instead of Step 10,
extract pushfiles.zip onto your Windows computer. Extract the files from my initial post into the same folder.
Connect the phone, wait a little so Windows gets some time to find it.
Run recovery-windows.bat.
Continue from Step 13.
The recovery-windows.bat is downloadable from here http://www.laddaupp.nu/android/pushfiles-win-addon.zip
extract it to your pushfiles directory.
Get over there now and check it out for yourself!
P.s. i have no affiliation whatsoever with that website was just desperate for a simple solution and found it there.
and to the people who made that method possible, you are heros!
I played no part in their superb efforts. Just passing on their wisdom.
HTML:
http://www.machackpc.com/headline/ho...ndroid-os-2-1/
The link is wrong..
http://www.machackpc.com/headline/how-to-root-your-htc-desire-running-android-os-2-1/
link dead..
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
this guide is the same from paul......
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
I confirm it works. We should package up only the files required for entering into Recovery mode from Windows.
thanks for the heads up!
ok, my misstake.. it mean to extract all files to the same folder and run the *.bat file.. after you should find your phone in recovery mode.. ok... nice..
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
this is working link
http://www.machackpc.com/headline/how-to-root-your-htc-desire-running-android-os-2-1/
but i cannot download...
testruu.exe
pushfiles.zip
rootedupdate.zip
can anyone upload yhme in rapidshare or mediafire or somwhere else?
Dear all,
I try it out right now, and it works.. amazing.. ,) hehehe
extract all files in one folder, boot the phone in hboot(turn it off, turn it on whit hold power and volume button together),
choose recovery and after you see the red triangle run the *.bat.. ..and your phone is in amon_ra.. ,)
many thanks to the poster!!
sparklehedgehog said:
NOOBs or anybody struggling with this way of doing it listen up!!!!
P.s. i have no affiliation whatsoever with that website was just desperate for a simple solution and found it there.
Click to expand...
Click to collapse
m_adnan said:
Dear all,
I try it out right now, and it works.. amazing.. ,) hehehe
extract all files in one folder, boot the phone in hboot(turn it off, turn it on whit hold power and volume button together),
choose recovery and after you see the red triangle run the *.bat.. ..and your phone is in amon_ra.. ,)
many thanks to the poster!!
Click to expand...
Click to collapse
It works great
had it anyone tested with the 0.80 firmware? or will this really not work? know anyone, who can i buy an Desire with the 0.75 firmware in germany?
i think its not necessary to buy a new device, i mean that the guys will find a way out to root a desire whit .80 too. my desire run whit .75 version, and i think its better to not test.. *smile sorry, my english is bad.. hehehehehhe
florifliegt1 said:
had it anyone tested with the 0.80 firmware? or will this really not work? know anyone, who can i buy an Desire with the 0.75 firmware in germany?
Click to expand...
Click to collapse
here, i uploaded all files to rapidshare. the "noob rooting method" is allready in pushfiles folder. works great, dont need linux-live cd more. nice work!!
(sorry for my english )
rapidshare.com/files/382833165/Desire_root.part1.rar
rapidshare.com/files/382839560/Desire_root.part2.rar
Edit:
App2SD is included
RealUnknown said:
this is working link
http://www.machackpc.com/headline/how-to-root-your-htc-desire-running-android-os-2-1/
but i cannot download...
testruu.exe
pushfiles.zip
rootedupdate.zip
can anyone upload yhme in rapidshare or mediafire or somwhere else?
Click to expand...
Click to collapse
http://www.wright-pc.com/pyr0/HTC DESIRE/r1/
I wanna root my desire badly, but don't wanna end up bricking it.. is this current windows method 100% guaranteed to not cause any issues? and does apps2sd work also?
Pyr0x64 said:
http://www.wright-pc.com/pyr0/HTC DESIRE/r1/
Click to expand...
Click to collapse
Thank you, just what I was looking for.
koolbear said:
I wanna root my desire badly, but don't wanna end up bricking it.. is this current windows method 100% guaranteed to not cause any issues? and does apps2sd work also?
Click to expand...
Click to collapse
with the windows method you can open recovery without linux or mac and it's done rooting more easier than before. if you use paul's instructions with the windows methode, you can't do much wrong. yes, app2sd works.
ogeeEn said:
with the windows method you can open recovery without linux or mac and it's done rooting more easier than before. if you use paul's instructions with the windows methode, you can't do much wrong. yes, app2sd works.
Click to expand...
Click to collapse
thanks bro, i will give it a go now, btw is the apps2sd u used the same one posted by paul?
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
Update 12/31/2012 CM10.1
Thanks to Exxodium for swapping devices with me. I got the Photon-Q yesterday and have had a little time to work with it. Last night I built an insecure kernel so I could have adb as root. Moments ago, after losing all my junk and all the stuff that has happened in the last month, I built CM10 with inline kernel. Skip to the good stuff. I was able to get a partial boot; enough to get a logcat and last_kmsg to do some debugging. I will not be posting any links until I have a fully booting device, and even then not before I have some private testing done. Stay tuned. Cheers and out!
The link to the flashable.zip doesnt seem to be working
edit it works just have to remove the second http: from the link there
Sent from my XT897 using Tapatalk 2
That's what I assumed but I'll still fix it as soon as I get home. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
Definitely going to try this after I recharge.
Edit: tried the flashable. It failed in twrp. Maybe the download wasn't complete?
Edit part 2: re-downloading.. Gonna try again.
Edit part 3: re download did not work. Still failed. Anyone else?
Edit part 4: tried fastboot
C:\Program Files\Android\android-sdk\tools>moto-fastboot flash system cm10_photo
n_q_pre-alph.asystem.img
sending 'system' (187108 KB)... OKAY [ 87.646s]
writing 'system'... INFOUnknown chunk type
FAILED (remote failure)
C:\Program Files\Android\android-sdk\tools>
Sent from my XT897 using xda premium
tetrabyt said:
Definitely going to try this after I recharge.
Edit: tried the flashable. It failed in twrp. Maybe the download wasn't complete?
Edit part 2: re-downloading.. Gonna try again.
Edit part 3: re download did not work. Still failed. Anyone else?
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Mine failed in TWRP too...good thing I made a backup...lol
zrmxp95 said:
Mine failed in TWRP too...good thing I made a backup...lol
Click to expand...
Click to collapse
It would help if you gave me a little more information, like error codes, when you post reports.
why does everyone keep thanking me? i play halo and borderlands 2 and yell at kids on my lawn. i do nothing else!
shabbypenguin said:
why does everyone keep thanking me? i play halo and borderlands 2 and yell at kids on my lawn. i do nothing else!
Click to expand...
Click to collapse
Hey now, who started the asanti device tree? Dats right. Who compiled the first kernel from source? Dats right. Who made a flashable zip just so I could kang it for my kernel!??!
I rest my case.
interloper said:
It would help if you gave me a little more information, like error codes, when you post reports.
Click to expand...
Click to collapse
From what I remember I just said error....no codes......I can try it again later today and see after I run errands around town
interloper said:
It would help if you gave me a little more information, like error codes, when you post reports.
Click to expand...
Click to collapse
didnt give a error on install just aborted but did notice when you just try and extract the file it gives error saying file is already there like 5 times
in folder
system\etc\terminfo\
Alright lads, head on to the new link and give it some welly! I rebuilt the system with changes to the vendor side, fixed the install script and a few other jelly rolls. Let me know what happens.
Using this link :
Gives format() expects 5 arguments, got 4.
E:Error in /sdcard/cm-10-(etc etc) (Status 7).
UPDATE
Ok, I fixed a few things so the ROM should flash properly. Remember to wipe properly or you'll get a rash. Cheers!
Didn't work for me
I tried flashing it this morning and all I got was some looping flickers, Never even a moto logo... So not sure.
I've done a couple builds that have not been posted in this thread, for private testing. I am doing my best, but without testers committed to helping me fix this, it won't be me who puts out CM10. I'm working with arrrghh and lmartin but they are only on a limited amount of time. No one is giving me logs, kmsg, dmesg etc, and if that doesn't happen, all I can do is guess. If you are interested in testing, I am committed to getting CM10 out for this device.
interloper said:
I've done a couple builds that have not been posted in this thread, for private testing. I am doing my best, but without testers committed to helping me fix this, it won't be me who puts out CM10. I'm working with arrrghh and lmartin but they are only on a limited amount of time. No one is giving me logs, kmsg, dmesg etc, and if that doesn't happen, all I can do is guess. If you are interested in testing, I am committed to getting CM10 out for this device.
Click to expand...
Click to collapse
IIRC, I couldn't get adb up on your build... So I was unable to pull logs.
I did provide you a last_kmsg, but that's about all I could do without adb.
I kinda wish I knew more about how to fit the pieces of CM together better, as I think CM9 would be done if I did
Updated OP. I think it's still gonna boot loop, and if so please try adb. If adb works please try and get a logcat or dmesg. If you need help getting adb setup, need to know the commands to use adb, or have any other questions, please chat with me on IRC. Good luck.
interloper said:
Updated OP. I think it's still gonna boot loop, and if so please try adb. If adb works please try and get a logcat or dmesg. If you need help getting adb setup, need to know the commands to use adb, or have any other questions, please chat with me on IRC. Good luck.
Click to expand...
Click to collapse
I didn't have any luck getting adb to recognize the 10-08 build. Installed and booted past boot logo, then looped between black screen & screen off.
fallnSaint said:
I didn't have any luck getting adb to recognize the 10-08 build. Installed and booted past boot logo, then looped between black screen & screen off.
Click to expand...
Click to collapse
Thank you. Check back tonight for a new build, if you would.
Does it boot into recovery? Would you mind testing some kernels on IRC later tonight?
Updated the OP with a new attempt. Following newer CM "lets have everything in common that's common" there is a bit more merging in the code base. While this means nothing to the end user in general it means that IF this get working properly it will more likely get to be official. That is significant. Official means more people get to enjoy it served up from a nice list of perfectly good links from an organized website. As an end user myself, that excites me. So, here's to hoping the stupid thing boots because as humiliating as this is, I think quitting now would be even worse.
1. Make a backup
2. Flash the zip in recovery.
3. WIN or LOSE!
4. Let me know what happened with as much detail as possible.
5. I'm going to get some sleep now maybe.
Progress circles keep circling til battery dies. Coldboot didn't work. (Although Asus said I shouldn't try android icon.)
Don't want to wipe data if I don't have to because I was in the middle of backing up data when it got stuck (can I connect it to my 2 1/2 yr. old laptop to copy files I need?)
Have all updates except last one two weeks ago. Not under warranty.
hi
Try to connect it to PC when you turn it on..if your computer recognized it...other wise no way to copy data as far as i know..(I am also not a PRO).
For your tablet to boot again i think go into recovery and then wipe everything and it ll re format your tablet then it should be in factory condition.
If this dosent works try my guide see the first posts in here u ll find it!!..
Hope u ll recover it!
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Can't Find adb download link
UndisputedGuy said:
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
pjspener said:
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
Click to expand...
Click to collapse
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
How to find Link to sdk with adb
UndisputedGuy said:
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Forgive my ignorance. That link didnt lead me to an sdk with adb in the directories, which sdk do I use?
Also, I cant figure out how to get a list of the guides on this forum or all forums.
Thanks!
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
adb devices command didnt work
UndisputedGuy said:
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
Click to expand...
Click to collapse
"adb devices" didn't work for me either, how did you make it work? I'm in the same place you were.
Also are there separate adb drivers?
Thanks
Hey guys, first of all sorry for my bad english, its not my mothers language.
I unlocked my bootloader of my Nvidia Shield LTE version and installed TWRP. After that, i run the recovery mode, wiped everything (no OS) and tried to install new ROM. But during this, the console told me, that the .zip is for device shieldtablet and my device is . <---- yeah, no name given.
So i guess twrp cannot notice that this is a shield, and therefore i cannot install another rom and another OS. Now i cannot do anything..
Any ideas?
Hope you can help. Have a nice weekend
Tim
wafebreaker said:
Hey guys, first of all sorry for my bad english, its not my mothers language.
I unlocked my bootloader of my Nvidia Shield LTE version and installed TWRP. After that, i run the recovery mode, wiped everything (no OS) and tried to install new ROM. But during this, the console told me, that the .zip is for device shieldtablet and my device is . terminal
there enter:
setprop ro.product.device shieldtablet
setprop ro.build.product shieldtablet
then you can flash.... i will tell the maintainer
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
sorry i am new in this area. How and where can i enter those commands?
Thx for help
wafebreaker said:
sorry i am new in this area. How and where can i enter those commands?
Thx for help
Click to expand...
Click to collapse
within twrp
advanced-> terminal
Sent from my Xperia T using XDA Free mobile app
Okay first of all, thanks a lot. Because of you i started searching for those key words you wrote. And i find a solution.
Found another solution, but yours works fine too
For everyone else having this problem:
Go into your .zip with winrar (or something else), go to META-INF/com/google/android and extract the updater-script.
Open it with notepad++ and delete every line with "getpro(xyz)" and insert it again into your .zip
There you go, it works.
Thx alot )
wafebreaker said:
Okay first of all, thanks a lot. Because of you i started searching for those key words you wrote. And i find a solution.
Found another solution, but yours works fine too
For everyone else having this problem:
Go into your .zip with winrar (or something else), go to META-INF/com/google/android and extract the updater-script.
Open it with notepad++ and delete every line with "getpro(xyz)" and insert it again into your .zip
There you go, it works.
Thx alot )
Click to expand...
Click to collapse
There is a new version on the XDA thread that fixes all this.... :good:
Thx Josh
lj50036 said:
There is a new version on the XDA thread that fixes all this.... :good:
Thx Josh
Click to expand...
Click to collapse
hello
which thread is it the helps fix this problem?
Paracel said:
hello
which thread is it the helps fix this problem?
Click to expand...
Click to collapse
http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Thx Josh
lj50036 said:
http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Thx Josh
Click to expand...
Click to collapse
thanks!
wafebreaker said:
Hey guys, first of all sorry for my bad english, its not my mothers language.
I unlocked my bootloader of my Nvidia Shield LTE version and installed TWRP. After that, i run the recovery mode, wiped everything (no OS) and tried to install new ROM. But during this, the console told me, that the .zip is for device shieldtablet and my device is . <---- yeah, no name given.
So i guess twrp cannot notice that this is a shield, and therefore i cannot install another rom and another OS. Now i cannot do anything..
Any ideas?
Hope you can help. Have a nice weekend
Tim
Click to expand...
Click to collapse
I tried to revive my recalled shiled last night and did the same thing formatted the system and did not make a backup ahahahah im ****ed but i can get to twrp