Related
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.
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
ProfessorAnomaly said:
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
Click to expand...
Click to collapse
I might be willing to help. What is it you are wanting to do?
peppy6582 said:
I might be willing to help. What is it you are wanting to do?
Click to expand...
Click to collapse
I'd like somebody to test the custom recovery I've compiled, and to make sure it works properly.
ProfessorAnomaly said:
I'd like somebody to test the custom recovery I've compiled, and to make sure it works properly.
Click to expand...
Click to collapse
I don't intend to be rude, but what is your comfort level of non-brickage?
peppy6582 said:
I don't intend to be rude, but what is your comfort level of non-brickage?
Click to expand...
Click to collapse
There is no risk in bricking your device. You simply just have to boot the recovery.img and make sure it works.
Code:
fastboot boot recovery.img
7778c713fe675747fc4ce937fd40fe2e recovery.img
Download retracted for the time being.
ProfessorAnomaly said:
There is no risk in bricking your device. You simply just have to boot the recovery.img and make sure it works.
Click to expand...
Click to collapse
Yes, I will try. You have a pretty good track record! I had to check first, because I really like this thing!
Simply boot the image with fastboot and make sure that ClockworkMod Recovery is displaying properly on your TV. This way when you reboot your device nothing will have been changed, so there is no risk involved.
peppy6582 said:
Yes, I will try. You have a pretty good track record! I had to check first, because I really like this thing!
Click to expand...
Click to collapse
I appreciate your help! I have experience, so if you do encounter problems along the way I am available to help.
ProfessorAnomaly said:
I appreciate your help! I have experience, so if you do encounter problems along the way I am available to help.
Click to expand...
Click to collapse
I can see the device (adb devices), but when I do the fastboot command, it says waiting for device.
peppy6582 said:
I can see the device (adb devices), but when I do the fastboot command, it says waiting for device.
Click to expand...
Click to collapse
You must run this command first:
Code:
adb reboot bootloader
Followed by:
Code:
fastboot boot recovery.img
ProfessorAnomaly said:
You must run this command first:
Code:
adb reboot bootloader
Followed by:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Had to unlock it first. Nevermind. It booted into Android system recovery <3e>
peppy6582 said:
Had to unlock it first. Nevermind. It booted into Android system recovery <3e>
Click to expand...
Click to collapse
Alright, I will check my source again and recompile. I must have made a mistake along the way. If you're interested I'm also working on an auto-root that will be ready here shortly.
Do you have a gmail so that I could correspond with you via Hangouts? (If so, could you private message it to me?)
ProfessorAnomaly said:
Alright, I will check my source again and recompile. I must have made a mistake along the way. If you're interested I'm also working on an auto-root that will be ready here shortly.
Do you have a gmail so that I could correspond with you via Hangouts? (If so, could you private message it to me?)
Click to expand...
Click to collapse
I pm'ed you
I am also willing to assist if needed. I am comfortable with adb and fastboot.
I'm pretty comfortable with ADB and Fastboot. I wouldn't mind testing some stuff if you need me to.
Google already posted the factory images for the Nexus Player, so I don't mind. I'm interested in seeing what is possible with this little hockey puck.
Please add me to your list of candidates. I'd be very interested in checking out what you've got. Thanks.
ProfessorAnomaly said:
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
Click to expand...
Click to collapse
willing to help, should you still need.
If you still need another tester tell me.
I've already worked with headless CWM during my work on the ADT1 (controlling CWM entirely via adb, I have no keyboards that work with it)
I've been trying to avoid compliling CWM myself as I dont want to have rebuild my dev vm just to compile CWM
(I've built CWM 6.0 in the past, but it was years ago)
Currently need access to a booting (doesn't matter if the CWM parts work, all I need is a root shell) image to dump the initial rom.
Fortunately, since we already have factory images, at least I/someone wont need to prepare a flashable zip for it to restore.
TheManii said:
Currently need access to a booting (doesn't matter if the CWM parts work, all I need is a root shell) image to dump the initial rom.
Fortunately, since we already have factory images, at least I/someone wont need to prepare a flashable zip for it to restore.
Click to expand...
Click to collapse
What are you trying to dump that's not in the factory images?
Hi all, did anyone build a recovery? I would do it but I haven't got a computer that runs Linux and I am not firm with it at all.
Edit: I couldn`t use any method that I found to create a custom recovery, is there anyone with more success?
Also I could not use SP-Flash tool to make a backup, did anyone succeed and how?
Thanks
Sent from my HTC One A9 using XDA-Developers mobile app
new device ordered hopefully we see some development in this section soon =)
i also hope but i think this was not the interessted phone for developper...
Is there nobody to do this recovery?
Brainwasher34 said:
Is there nobody to do this recovery?
Click to expand...
Click to collapse
We gotta wait
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Captain_Throwback said:
If anybody cares about this and is willing to test some blind builds of TWRP, let me know (by replying here).
Click to expand...
Click to collapse
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
patrixs94 said:
I am interested in testing some builds of twrp on my a9s, are your offer still available?
Greetings.
Click to expand...
Click to collapse
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Captain_Throwback said:
Well, a month has passed, and I've forgotten everything I knew about this device, but I'll give it a shot when I have a chance. Stay tuned.
EDIT: It seems a month ago I built a test recovery for this device, but was waiting for a response before posting it. So @patrixs94 I'm attaching it here. Give it a try and let me know if it boots, and if so, I'll need a recovery log from it.
Click to expand...
Click to collapse
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
Click to expand...
Click to collapse
patrixs94 said:
Ok, I will test it. Have one question - is it safe? In case of bootloop occurs, do you have any idea how to exit it? Can't find any RUU in web - that was the way I ever exit it, and by this way I was restoring official software. Is there any another way?
---------- Post added at 01:19 PM ---------- Previous post was at 12:56 PM ----------
Ok, I founded one, but it does not fit to my mid/ cid . And I dont have s-off :/
Click to expand...
Click to collapse
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Tested
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Captain_Throwback said:
Flashing recovery shouldn't bootloop your device. Recovery is an entirely separate partition. You can try using "fastboot boot recovery.img" to see if that works, as that won't change anything on the device, but not all devices support it.
Honestly though, if you're not comfortable enough to test this, then there's no reason for me to work on this. Like I said, I know next to nothing about this device, so I need someone that can help me debug and provide logs, etc. Otherwise this exercise is futile.
Click to expand...
Click to collapse
vejda said:
Hi,
thank you, it´s great you are working on TWRP for this phone! I have tried to use it. After download it says booting on notebook and Start downloading on phone:
C:\fastboot\ fastboot boot recovery.img
downloading `boot.img`......
OKAY (1.453s)
booting...
After hard restart the phone works again.
Does it helps you?
T.
Click to expand...
Click to collapse
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Captain_Throwback said:
All that tells me is that your device doesn't support fastboot boot. So you'll need to flash it to test whether it works or not.
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
vejda said:
Thx. Flashed, after booting to recovery mode there is start screen, but I am not able to swipe to unlock it. Where can I find the log? Is it something like db.fatal.dbg?
Click to expand...
Click to collapse
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Captain_Throwback said:
/tmp/recovery.log
Is adb working? If so, you can adb pull the above file. Then I can at least see how much is working (besides touch being broken).
Click to expand...
Click to collapse
vejda said:
Yes, ADB works, but the file doesn´t exist (with the way /tmp/recovery.log). Only general bugreport, attached.
Click to expand...
Click to collapse
The recovery log has to exist while in TWRP.
ADB doesn´t run while TWRP, screen attached.
Captain_Throwback said:
The recovery log has to exist while in TWRP.
Click to expand...
Click to collapse
vejda said:
ADB doesn´t run while TWRP, screen attached.
Click to expand...
Click to collapse
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Ok, thx. I am not expirienced user of it, but try to solve it Where are all the others? Hey!!
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse
Here it is!
Here is the log, I was using old ADB.
Captain_Throwback said:
That error is on the computer side, not on the device. Fix your adb on your computer and then try adb in TWRP again.
Click to expand...
Click to collapse