So got an interesting issue
My c6603 has no usb port (broke)
BUT does have full root running existance and can access adb via wifi
The problem i have is i haven't used recovery for a while and wanted to upgrade to lolipop (ExistanceY).
If i reboot i cant get into it and there is no pink light
Using shell to reboot to recovery, a shortcut or adb also does not work. just boots up as normal.
Any ideas
I have tried reimaging fotakernel with TWRP but nothing. the recovery installers dont work either they either come up that they cant find the partition or doesn't have an image for the device or comes back as successfull
Hi, thank you for using XDA Assist. Your best bet is to ask in your device specific forum, which I see you know where it is. But just in case, http://forum.xda-developers.com/xperia-z. They are the experts on your device. But you have another issue too. Since 5.x you have to be stock, no root, for the updates to work. Check you device specific forum for more information.
cheers, that page is actually open in my other tab, created a new post in the wrong one. my bad. again cheers
Thread closed.
Related
I have been searching for answer over 10 days, but still can't figure out how to resolve this. I don't how exactly it bricked, it just couldn't start anymore. I can get into recovery menu, but there isn't any option to recover android. It was rooted before, and worked normally. I cant find any other way to flash any rom on it. I appreciate any help on this matter, tnx in advance!
XDA Visitor said:
I have been searching for answer over 10 days, but still can't figure out how to resolve this. I don't how exactly it bricked, it just couldn't start anymore. I can get into recovery menu, but there isn't any option to recover android. It was rooted before, and worked normally. I cant find any other way to flash any rom on it. I appreciate any help on this matter, tnx in advance!
Click to expand...
Click to collapse
Hello, and welcome to XDA Assist!
Please register for an account so you can post to the rest oif the site. The [Ask Any Question][Newbie Friendly] thread of the > Android Development and Hacking > Android Q&A, Help & Troubleshooting will provide a good start to resolve your issue.
What seems confusing is that there may be some Arnova's made by Archos. Archos has a forum, but sadly, Arnova does not (not finding much about your device either).
At any rate, try the thread/forum above, and be patient with regard to a response. This seems to be a rare device, so it would be harder to get the attention you need.
Hope this helps, and good luck!
The other way
I understood that the complete system is wiped out. I can use adb while its in recovery menu. I used it to transfer official system image onto it, but in its options i cant find it. I transferred it to multiple locations, all of them can be seen in recovery menu but all are empty. I wonder if there is a way to flash some other android version on it? Or some ROM like CWM, but apparently there are no official releases. And since i am not very good at this i wonder how to make sure that kernel is OK? Can such thing be done? It has Android system recovery <3e>
Ricci2u said:
I understood that the complete system is wiped out. I can use adb while its in recovery menu. I used it to transfer official system image onto it, but in its options i cant find it. I transferred it to multiple locations, all of them can be seen in recovery menu but all are empty. I wonder if there is a way to flash some other android version on it? Or some ROM like CWM, but apparently there are no official releases. And since i am not very good at this i wonder how to make sure that kernel is OK? Can such thing be done? It has Android system recovery <3e>
Click to expand...
Click to collapse
CWM is a recovery, not a ROM, but can be used to flash ROMs.
With 3e, you should be able to flash the stock ROM for the device via adb (called side loading). So that may work for you.
Hope this helps.
Sent from my ASUS ZenFone 2
Iv seen plenty of threads about this but can seem to find a straight answer for my issue specifically.
Like an idiot I wiped the system and internal storage, hence having no OP.
It's also saying my phone is no longer rooted and tries to install superSU but obviously fails.
I currently have no access to a laptop, just my android tablet. Am I able to download firmware and flash it while in twrp in order to boot back into the standard Sony Z2 android software. My model number is D6503
Ac715 said:
Iv seen plenty of threads about this but can seem to find a straight answer for my issue specifically.
Like an idiot I wiped the system and internal storage, hence having no OP.
It's also saying my phone is no longer rooted and tries to install superSU but obviously fails.
I currently have no access to a laptop, just my android tablet. Am I able to download firmware and flash it while in twrp in order to boot back into the standard Sony Z2 android software. My model number is D6503
Click to expand...
Click to collapse
Hi, thanks for using XDA Assist!
Please post your question here:
http://forum.xda-developers.com/xperia-z2/help
Your device experts are located there.
Good luck!
Thread closed.
I don't really know why my phone is stuck in a bootloop to begin with. I've tried EVERYTHING I could possibly think of!
Here's What I've tried :
WipeData/Factory Reset and I also wiped Cache.
I tried to use ODIN to flash the original stock ROM to the device but the bootloader is locked so its impossible to flash any ROM to the devices (Even if it's official).
I tried to apply the Lollipop 5.0 update in recovery using a external SD card.
I tried using ADB sideload.
(Bonus points if you can give me away to unlock the bootloader! because i'll know what to do if it's unlocked.)
So...If anyone has suggestions, I'll happily take any!
Also Please! Leave links so I have quick access!
Hi,
I can't find a relevant thread on your device and issue, but you can ask for help here,
http://forum.xda-developers.com/android/help
Good luck!
Hi,
I recently bought an Umi Iron and believe I have accidentally managed to soft brick it (based on what ive found on google and the forums here) I need a way to get it working again and have some ROMS (2 official ones) which are compatible for the device. The device will boot into recovery and allows restoration from an SD card, ABD Push or the cache. The cache is empty and although i have searched for how to do it from an SD card i have found no information (I've tried putting the .zip files onto the device and installing those but the device says "installation aborted"). I have a SDK which I am attempting t learn to use in order to fix the device. Any information about how to use the program/get the new ROM flashed via fastboot would be much appreciated as I have very little knowledge of what I am doing as I have never attempted to root or flash a phone. The phone comes pre rooted from the factory (I dont know if this info is relevant but I'm working on the assumption the more info i can give the better). The device entered this startup loop when i removed an app which i had accidentally installed as a system file while trying to use an app to move it to my SD card. Any information and help is much appreciated
Hi,
I can't find anything relevant on XDA for your device and issue, but perhaps the members in this thread can help..
http://forum.xda-developers.com/android/general/umi-iron-unibody-alloy-dual-led-t3127905
Good luck!
Hi Darth,
Many thanks for your reply, since i posted this thread I have done some further research and narrowed the problem down further. The device runs android 5.1 and there is a setting in the developer settings which locks the OEM bootlocker. This is the issue i am having. Because the device has this option checked, I cannot unlock the bootloader to install a custom rom to rectify the issue as i cannot turn the device on to access these settings. I have seen many people have had this problem with devices and android 5.1 including Nexus and HTC phones. I have been unable to find a fix for this issue though so if you know of any articles which may point me in the direction that would be most helpful
Thanks again
I would say the best place to ask about that is in the thread I linked above. But if that's not helpful, you could ask here,
http://forum.xda-developers.com/showthread.php?t=2257421
Every device is different as far as if or how the bootloader can be unlocked. So you really need an answer specific to your device.
Hope it works out for you!
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
XDA Visitor said:
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
joel.maxuel said:
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
jasj0410 said:
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
Click to expand...
Click to collapse
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
joel.maxuel said:
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
Click to expand...
Click to collapse
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
jasj0410 said:
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
Click to expand...
Click to collapse
Hello,
Fastboot is unable to flash zips unfortunately. That's the recoveries job.
If you can find fastboot images of stock, you can flash back that way.
Especially at this point, I would urge you to take advantage of the help thread I mentioned earlier. They know more about your device (particularly what's available and what not) they I would.
Hope this helps!