Related
hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.
you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery
Ive checked other nexus 7 threads... but this isn't the case.
My nexus 7 is stuck on the google Boot I cannot rub Fastboot or recovery from the toolkit .. nothing at all. It cant find the device .
When I plug in the usb it still makes the sound on windows and so on.
It happened when I was prepairing to install a Custom ROM using JROMFlasher..
I followed all the steps, and when it came to install the ROM to the SD card it just rebooted (transferred to quickly I thought)
And then Ever since it has Just been stuck on the google screen.
I am quite pissed :L
Any Ideas?
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Download the zip located here : platform-tools.zip Extract the contents to a folder name the folder Nexus7 or whatever you want.
Once thats done go ahead and open a command prompt window in that folder you can do that by Shift+Right clicking inside the folder and selecting "Open Command Prompt Here" or if on XP then open CMD and
Code:
cd C:\Users\Name-of-User\Desktop\Nexus7
Once in the CMD issue the command
Code:
fastboot devices
To see if the computer recognizes the device in fastboot mode. It should spit out a gibberish looking code with ....... Device at the end.
Then you going to flash the recovery to do that you issue this command
Code:
fastboot flash recovery name-of-recovery.img
inside the zip the openrecovery-twrp-2.3.1.0.img that is what you will put in place of "name-of-recovery.img" it will show on the screen writing recovery when its done hit the volume up button until the "START" Turn to "Recovery Mode." Then hit the power button you will boot into recovery mode. Once in recovery mode place the ROM.zip you want to flash in the same folder as the stuff you extracted to.
Then issue this command
Code:
adb push Name-of-ROM.zip /data/media
Of course you will replace name-of-ROM.zip with the actual name of the ROM you are flashing. Make sure you also have a gapps packaged which can be found on goo.im/gapps/ latest package is gapps-jb-20121011-signed.zip you will want to adb push that as well.
IF all is done correctly you should be able to install that ROM please follow this procedure.
1. Go to Wipe
2. Factory Reset (this will delete all your apps and apps data not the sd card)
3.Wipe Cache Partition
4. Wipe Dalvik Cache
5. Format System
6. Go to install and find the two ROM.zip and Gapps package at the bottom of the root of the sd card (/sdcard0)
7. Select to flash the ROM and then the Gapps
8. Reboot
Click to expand...
Click to collapse
You should be good to go now.
ÜBER™ said:
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Click to expand...
Click to collapse
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
QuantumCipher said:
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
Click to expand...
Click to collapse
Its all good wrote you up a quick guide follow that and it'll get you back on track .
ÜBER™ said:
Its all good wrote you up a quick guide follow that and it'll get you back on track .
Click to expand...
Click to collapse
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
QuantumCipher said:
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
Click to expand...
Click to collapse
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
ÜBER™ said:
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
Click to expand...
Click to collapse
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
QuantumCipher said:
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
Click to expand...
Click to collapse
Acutally its a zip of multiple components not just png's. The bootaniamtion.zip as a whole is what makes up that boot up animation. If you want to change the bootanimation you would replace that entire zip with one that you want. And then set the permissions and reboot. Some will even have a flashable. In order to modify system files you need root and a root explorer. There are multiple on the play store i would recommend Root Explorer if you have the money otherwise ES File Manager or Solid Explorer.
Bricked after wiping with twc
When I look for fastboot devices, nothing happens...
where do I go from here?
http://forum.xda-developers.com/showthread.php?p=35777264
Sent from my Nexus 7 using xda premium
Hello everyone!
I tried to restore the stock image using Nexus 4 Tool Kit (both the original one and the Wug's one), and everytime I tried, the script stucked at "writing system".
I manually flashed system and userdata images with Wug's tool kit and everything went well but I only have 5Gb memory instead of 16.
Does anyone know why?
Try this http://forum.xda-developers.com/showthread.php?t=2033692
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Sent from my Nexus 4
OP...
In future, don't use a toolkit. Do it yourself
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
When going into recovery the warning sign is the splash screen for stock recovery. This likely means that you have not yet flashed a custom recovery yet, which is necessary to flash CM. First read this guide to unlock the bootloader (if you havent already), then flash a custom recovery (preferably TWRP). After you have installed the recovery, download CM as well as the latest gapps package and place them somewhere on your internal sd. Boot into recovery and go to the wipe menu, then swipe to factory reset. Finally flash the rom and gapps, and then reboot.
4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I am using the .bat file... I've also tried the toolkit, and both appear to use the same basic procedure, and they stop at "writing system" no matter what.
Does anyone happen to know how the .bat file and toolkit get access to the phone? ...because I can't see it in adb (I'm guessing it's because I can't boot the phone.) However I can get into fastboot and recovery modes on the device.
I cannot get the device (nexus 4) to boot or connect in ADB mode to my computer. What can I do??
UPDATE - PROBLEM FIXED
I un-bricked my phone
SOLUTION this is what worked for me, your mileage may vary
Install ADB drivers, etc. from Android SDK (google how to do this)
Flash custom recovery (can be done easily with Nexus 4 Toolkit here on XDA) - I used TWRP Touch Recovery.
Once that is done, shut the phone off completely and boot into Fastboot (hold volume down and power)
Use volume keys to select Recovery Mode, then hit Power
In recovery mode:
Wipe > Advanced Wipe > Check off the box beside "System" > Swipe to Wipe
Go back to recovery mode main screen:
Wipe > Format Data > Follow the instructions on the screen
I think this step is what did it. When having problems with partitions, just format everything and start over
Now we should be able to write to the System partition, meaning you can flash a ROM and get your phone to boot again.
Follow the rest of these instructions to quickly flash the stock Android image from Google onto your phone.
Go back to recovery mode main screen, once again:
Reboot > Bootloader > Follow any additional instructions it gives you
Download Google Nexus 4 factory stock image "occam" (Google it)
When that is downloaded, open it with 7zip. Inside there are some files, one of which is called image-occam-jdq39.zip. Inside are some images - unzip those as well. You'll need the system.img file in a bit...
Using Wug's Nexus Root Toolkit (Google it - install it on your Windows PC):
Open the program
Launch advanced utilities
Hit the System button to permanently flash to System partition. Hit "ok" on the window that pops up.
Find the system.img file I mentioned back on step 10 and select that, when prompted, and open it.
If all went well, your device will now boot into the stock Android ROM.
noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Soundchasr said:
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Click to expand...
Click to collapse
The system takes awhile to write, how long have you guys wait before you say its "stuck"?
Sent from my Nexus 4 using Tapatalk 4 Beta
About 20-25 minutes.
Yea, that's way too long.
Sent from my Nexus 4 using Tapatalk 4 Beta
Stuck, but working
I was flashing the 4.3 image using the included flash-all.bat (but I edited it to remove -w parameter so that it wouldn't wipe my data).
In the 'writing system' step, the command window got stuck. In the phone screen, at the bottom, it said 'writing' for a while and then that also went away. I waited for ~40 min, and still the command window was at 'writing system', so I closed the command window, and booted my phone by selecting start from the bootloader.
And voila! It worked. Booted in under a minute, the flash was a success, I got JB 4.3 without losing any of my data.
Lost my root and custom recovery though. But I knew that would happen. Gonna try SuperSu for 4.3 now, after flashing TWRP.
Had the same problem, tried everything! With my tiny powers, but it kept stucking at "writing system" . I thought that I bricked the device, so for the last hope, I installed WugFresh's Nexus Toolkit and did a Fast Stock + unroot. It Installed everything flawlessly! I'm gonna donate to that guy! He's a godsend savior.
Michael Hall writes about how you can win an OPPO Find 5 by porting Ubuntu Touch to it!
http://mhall119.com/2013/08/win-an-oppo-find-5/
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
RaspberryJam said:
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
Click to expand...
Click to collapse
-True, but during XDA: DevCon we had 3 people without a phone produce images for it, and it's not a one-chance thing, you can resubmit as often as you like.
-How about this, if you already have a Find 5, give me the same of somebody who you think should get this one instead. Could be a friend, or somebody who's work in the XDA community you think should be rewarded.
Despite having three separate developers build images and flash them onto the phone, none were able to boot into Ubuntu Touch.
Click to expand...
Click to collapse
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
paperWastage said:
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
Click to expand...
Click to collapse
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Testers needed
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
mhall119 said:
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Click to expand...
Click to collapse
Throw your files and what youve done so far over here. Im willing to continue work on it.
Androguide.fr said:
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf_2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
Click to expand...
Click to collapse
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
SystemErrorOne said:
Throw your files and what youve done so far over here. Im willing to continue work on it.
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
Click to expand...
Click to collapse
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Androguide.fr said:
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Click to expand...
Click to collapse
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Androguide.fr said:
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Click to expand...
Click to collapse
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
SystemErrorOne said:
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
Click to expand...
Click to collapse
From your error message, you simply didn't add the .img extension to the twrp image
Also, you can't fastboot a zip, don't try.
But, did you try to simply do the following?
Code:
adb reboot recovery
There's absolutely no reason why it would have overwritten your recovery, my guess is you can't reboot to recovery using the button combination.
Anyway, if the above doesn't work, follow these steps to reflash your recovery:
Open a terminal on your pc
Make sure you cd to the directory where your twrp image is
issue the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-find5[COLOR="DarkRed"].img[/COLOR]
Reboot to recovery using:
Code:
adb reboot recovery
Are you on windows or linux?
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
+Franco Colomba I had no such issues with drivers. The only thing was ADB needed an extra USB VID added.
Click to expand...
Click to collapse
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
SystemErrorOne said:
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
Click to expand...
Click to collapse
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Androguide.fr said:
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Click to expand...
Click to collapse
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
SystemErrorOne said:
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
Click to expand...
Click to collapse
Try this:
Download a CM build
Open it with winrar and extract the boot.img from it
hold shift and do a right-click in the folder where you extracted the boot.img, and select "open a terminal here" (or whatever the header is)
Issue this command
Code:
fastboot flash boot boot.img
Now try again to reboot to recovery using the buttons combination
hurray so i managed to get the phone working by using a script found in that one thread you linked me too.. never the less i managed to get into TWRP and from there i had already made a backup (THANK GOD) and i restored and the phone is up and running perfectly. Now what Im going to do is what you instructed to do first.
1. the build first
2. then the ubuntu base afterwards
with
factory reset, wipe dalvik-cache
i will post back my results wish me luck
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
mhall119 said:
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
Click to expand...
Click to collapse
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
SystemErrorOne said:
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
Click to expand...
Click to collapse
Yeah, Michael Hall reported to me that the build doesn't boot either.
I'm working on a new build using a different toolchain, as with the stock Google TC I had to hack my around -Werror flags and this might be the problem.
I'll post the progress here.
Hi friends, I've found a way to root 10.4.B.0.577 android 4.3. Please see the instructions below:
Prerequisite:
1. Download SuperSU flashable at: http://download.chainfire.eu/351/
2. Download extract the boot.img from CM10.2 (attached as well)
3. Download the install fastboot
Steps:
1. Flash the stock ROM of 10.4.B.0.577
2. Put the Tablet Z in fastboot mode (press and hold Vol+ when inserting USB cable)
3. Open a console where the fastboot.exe is located, type
fastboot flash boot boot.img
fastboot reboot
4. Keep pressing Vol+ for a few times it boots up
5. Install SuperSU as normal
6. Power off the device
7. Flash the stock ROM of 10.4.B.0.577 again BUT EXCLUDE the SYSTEM
8. Boot up and you will have the SuperSU installed
My device is unlocked, I'm not sure if this works for locked bootloader as well. Try at your own risk! This method should work for both WIFI and LTE models.
[Files uploaded again, change 001.boot.zip to boot.zip.001 and do the same to 002 unzip]
This method works fine but only with unlocked bootloader as if you are locked you cant flash boot.img from fastboot
pangiotis24 said:
This method works fine but only with unlocked bootloader as if you are locked you cant flash boot.img from fastboot
Click to expand...
Click to collapse
For Locked bootloader, the only working method atm is here http://forum.xda-developers.com/showthread.php?t=2588442, the files needed for all XTZ models ( 351,321,311,312) are there now
Unlock/Root/Relock BL
Hello!! Great job but i have a question!! Can we unlock the bootloader, root with your guide and then relock the bootloader?? It will be rooted after relock?
Attached files ?
Xyam said:
Hi friends, I've found a way to root 10.4.B.0.577 android 4.3. Please see the instructions below:
Prerequisite:
1. Download SuperSU flashable at:
2. Download extract the boot.img from CM10.2 (attached as well)
3. Download the install fastboot
Steps:
1. Flash the stock ROM of 10.4.B.0.577
2. Put the Tablet Z in fastboot mode (press and hold Vol+ when inserting USB cable)
3. Open a console where the fastboot.exe is located, type
fastboot flash boot boot.img
fastboot reboot
4. Keep pressing Vol+ for a few times it boots up
5. Install SuperSU as normal
6. Power off the device
7. Flash the stock ROM of 10.4.B.0.577 again BUT EXCLUDE the SYSTEM
8. Boot up and you will have the SuperSU installed
My device is unlocked, I'm not sure if this works for locked bootloader as well. Try at your own risk! This method should work for both WIFI and LTE models.
Click to expand...
Click to collapse
Sorry, but when you say that the files are attached... attached to where ? can't see them anywhere. thanks in advance.
Installing SuperSU
Xyam said:
fastboot flash boot boot.img
fastboot reboot
4. Keep pressing Vol+ for a few times it boots up
5. Install SuperSU as normal
.
Click to expand...
Click to collapse
Sorry for asking again, I'm new and I'm struggling with this. I tried to follow your steps (my tablet is a SGP312). I followed the steps, but I'm not sure if the ZIP file with SuperSU has to be downloaded to the tablet or what, as in step 5 you say "install SuperSU as normal". Does that mean through play store ? Directly from the file ? If it´s from the file, how ?
When I tried this in my tablet, after flashing boot.img and rebooting, I got a loader screen where I selected add super used, rebooted, and then... the tablet didn´t start again. It gets stuck in the initial booting screen with the color lights passing.
Also, I noticed that after the fastboot reboot, the message that I got in the loader mentioned SGP311, not 312. Any help would be much appreciated. Thanks.
TheRealAlexei said:
Sorry for asking again, I'm new and I'm struggling with this. I tried to follow your steps (my tablet is a SGP312). I followed the steps, but I'm not sure if the ZIP file with SuperSU has to be downloaded to the tablet or what, as in step 5 you say "install SuperSU as normal". Does that mean through play store ? Directly from the file ? If it´s from the file, how ?
When I tried this in my tablet, after flashing boot.img and rebooting, I got a loader screen where I selected add super used, rebooted, and then... the tablet didn´t start again. It gets stuck in the initial booting screen with the color lights passing.
Also, I noticed that after the fastboot reboot, the message that I got in the loader mentioned SGP311, not 312. Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
you have to flash the SuperSU .zip file via CWM. Do you know how to enter CWM and flash a .zip file?
Vaggelis AsKyE said:
you have to flash the SuperSU .zip file via CWM. Do you know how to enter CWM and flash a .zip file?
Click to expand...
Click to collapse
I think through the fastboot reboot, pressing the vol up. When I tried it before I entered in some kind of boot menu, with one option been "install from zip" or something like that but I didn´t try it.
I tried entering in it again and clicked on factory reset hoping that would do a cfresh install, but I still have the same issue: when powering up the tablet it keeps displaying the intro (the color lines) endlessly
TheRealAlexei said:
I think through the fastboot reboot, pressing the vol up. When I tried it before I entered in some kind of boot menu, with one option been "install from zip" or something like that but I didn´t try it.
I tried entering in it again and clicked on factory reset hoping that would do a cfresh install, but I still have the same issue: when powering up the tablet it keeps displaying the intro (the color lines) endlessly
Click to expand...
Click to collapse
you have to follow the guide!! at the step u flash boot.img and restart the tablet you must press rapidly many times to enter the boot menu. There u chose install from zip and find the file SuperSU.zip (i recommend u to use external sd card to save the SuperSU.zip file). When it finish u go back and find the ''Advanced'' option on the boot menu, u press it and then press power off. Then flash the stock ROM of 10.4.B.0.577 again BUT EXCLUDE the SYSTEM!!!
Vaggelis AsKyE said:
you have to follow the guide!! at the step u flash boot.img and restart the tablet you must press rapidly many times to enter the boot menu. There u chose install from zip and find the file SuperSU.zip (i recommend u to use external sd card to save the SuperSU.zip file). When it finish u go back and find the ''Advanced'' option on the boot menu, u press it and then press power off. Then flash the stock ROM of 10.4.B.0.577 again BUT EXCLUDE the SYSTEM!!!
Click to expand...
Click to collapse
Thanks for your help. Actually I managed to do it pretty much as you said) except the advanced -> power off, which I didn´t know: I assumed that was the way to access the boot menu, and to install Super SU, so I copied the ZIP into my external SDCard, did all the steps, and my tablet came back to life... with SuperSU installed
Lucky me I did a full backup following another guide, because in my desperation to bring my tablet back to life I did a full wipe out / factory reset (which btw didn´t solve anything).
Thanks for your replies and apologies if my questions seemed dumb... It's been many years since I "almost" break a device and lost all the data
TheRealAlexei said:
Thanks for your help. Actually I managed to do it pretty much as you said) except the advanced -> power off, which I didn´t know: I assumed that was the way to access the boot menu, and to install Super SU, so I copied the ZIP into my external SDCard, did all the steps, and my tablet came back to life... with SuperSU installed
Lucky me I did a full backup following another guide, because in my desperation to bring my tablet back to life I did a full wipe out / factory reset (which btw didn´t solve anything).
Thanks for your replies and apologies if my questions seemed dumb... It's been many years since I "almost" break a device and lost all the data
Click to expand...
Click to collapse
Happy you made it!!! :good:
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
TheRealAlexei said:
Thanks for your help. Actually I managed to do it pretty much as you said) except the advanced -> power off, which I didn´t know: I assumed that was the way to access the boot menu, and to install Super SU, so I copied the ZIP into my external SDCard, did all the steps, and my tablet came back to life... with SuperSU installed
Lucky me I did a full backup following another guide, because in my desperation to bring my tablet back to life I did a full wipe out / factory reset (which btw didn´t solve anything).
Thanks for your replies and apologies if my questions seemed dumb... It's been many years since I "almost" break a device and lost all the data
Click to expand...
Click to collapse
I have one question!! Does your tablet lag a little when it is closing? The bar loading at me and for 10 sec tablet freezes and then it close... do u experience the same issue??
TheRealAlexei said:
Sorry, but when you say that the files are attached... attached to where ? can't see them anywhere. thanks in advance.
Click to expand...
Click to collapse
Sorry just realized that XDA did not allow .001 and .002. Please download them again, change 001.boot.zip to boot.zip.001 and do the same to 002 to unzip. Alternatively you can download CM10.2 and extract the boot.img from the zip.
Vaggelis AsKyE said:
Happy you made it!!! :good:
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I have one question!! Does your tablet lag a little when it is closing? The bar loading at me and for 10 sec tablet freezes and then it close... do u experience the same issue??
Click to expand...
Click to collapse
did you mean shutting down or what? if you are mentioning shutting down, i have the same issue, but not related to rooting. just wait for around 20~30 seconds after you see "shutting down"
Vaggelis AsKyE said:
Hello!! Great job but i have a question!! Can we unlock the bootloader, root with your guide and then relock the bootloader?? It will be rooted after relock?
Click to expand...
Click to collapse
i was thinking the same idea. but will only do that if i have a hardware issue and need repair at sony repair center
[/COLOR]
Xyam said:
did you mean shutting down or what? if you are mentioning shutting down, i have the same issue, but not related to rooting. just wait for around 20~30 seconds after you see "shutting down"
Click to expand...
Click to collapse
I chose shut down from the menu and the bar is loading. After a while tablet freezes and after 10-15 seconds tablet goes off
ok so
i have SGP311 with 10.4.B.0.577
i must have custom recovery to instal UPDATE-SuperSU-v1.86.zip or i can instal it in stock ?
Mr0czny said:
ok so
i have SGP311 with 10.4.B.0.577
i must have custom recovery to instal UPDATE-SuperSU-v1.86.zip or i can instal it in stock ?
Click to expand...
Click to collapse
if u flash boot.img with flashtool u will get custom recovery (CWM) installed!!!
Hello,
I have ever update my XTZ on 4.3 JB. Do you think it is necessary to "flashboot" again the new firmware (Step 7) after install of Supersu.zip ?
If yes, can you explain why ?
Thanks for your help
strung3 said:
Hello,
I have ever update my XTZ on 4.3 JB. Do you think it is necessary to "flashboot" again the new firmware (Step 7) after install of Supersu.zip ?
If yes, can you explain why ?
Thanks for your help
Click to expand...
Click to collapse
Hello,
At this guide u flash boot.img from CM10.2 ROM (Step 3). At the end you have to reflash the new firmware so the boot, kernel etc change, because if u stay with CM10.2 u will get bootloops!!
Vaggelis AsKyE said:
If you unlock bootloader you can't use music info download and Bravia engine also. Although, I unlocked my bootloader and I followed your guide rooting successfully my Xperia Tablet Z SGP311 with .577 firmware. I used the latest flashtool to unlock the bootloader!!
When I finished all the process of rooting the music info didn't work so I tried to relock the bootloader with flashtool!! I did and guess what!! I have root with locked bootloader, stock firmware and working music info download!!!
You can make a guide that everyone with his own ftf can root his device just unlocking and locking the bootloader!!
The process must be done strictly with flashtool cause it keeps the keys for the relock!!!
Click to expand...
Click to collapse
Question: if you unlock the bootloader with Sony tools do you loose the music download info and the Bravia engine ????????