Related
Mistakenly I replaced /dev/mtd/mtd0 partition with dd command.
Now phone is not booting.
Am able to get into fastboot mod by using AdamOutler's Unbrickable mod applcation. But flashboot flash bootloader giving error
Code:
sending 'bootloader' (1536 KB)...
OKAY [ 0.210s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.318s
Even tried with ODIN (without re partitioning) , but it also failed when flashing bootloader.
I think I need to re-partition my device. Any one have (or know to generate) odin partition system file ?
Any other way or work around ?
* Am in india, and I dont think samsung sells I9020T here.
* I saw the post http://forum.xda-developers.com/showthread.php?t=947950
but i couldnt find necessary files there.
EDIT:
I able to fix it.
If you want to know how I fixed it, here is it.
1. Boot into fastboot mod via unbrickable mod application.
2. fastboot boot stock-recovery.img
3. flash stock rom
4. everything will be fixed.
What did you do to get your phone "bricked?" So you cannot get into the bootloader at all? Are you sure its download mode you are getting to? It is really really hard to brick a Nexus s...
Sent from my Nexus S 4G using xda premium
As long as you can get into download mode and your computer will recognize the phone you're not bricked. From download you can reflash all the files to get the phone back up and running through Odin.
I am not able to flash bootloader. Even odin fails to flash it. I think I need to re partition my device. But OPS file is not available any where. If you know how to make it, plase help me.
Is there any way to format the bootloader partition ? (using fastboot) ?
Rem3Dy said:
What did you do to get your phone "bricked?" So you cannot get into the bootloader at all? Are you sure its download mode you are getting to? It is really really hard to brick a Nexus s...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I mistakenly replaced /dev/mtd/mtd0 with dd command. :'(
Can any one give me a copy of /dev/mtd/mtd0 ?
(you can make that by 'dd bs=4096 if=/dev/mtd/mtd0 of=/sdcard/filename')
jishnu7 said:
My phone is now in completely bricked form. Am only able to get into download mod.
I saw a post http://forum.xda-developers.com/showthread.php?t=947950
but i couldnt find necessary files there.
Please share odin/ops and other necessary files.
Click to expand...
Click to collapse
Why you can not use AdamOutler resurector ? It's really really worked ...just try it and you'll see
Take a look here , it was my problem => http://forum.xda-developers.com/showthread.php?t=1474539
Good luck!
surdu_petru said:
Why you can not use AdamOutler resurector ? It's really really worked ...just try it and you'll see
Take a look here , it was my problem => http://forum.xda-developers.com/showthread.php?t=1474539
Good luck!
Click to expand...
Click to collapse
I am using that to bootup my device. But am not able to flash bootloader.
jishnu7 said:
I am using that to bootup my device. But am not able to flash bootloader.
Click to expand...
Click to collapse
OK!
B : try again ...and wait for image UnBrickable to change..than press ...Downloade Mode ...... you'll see ( where it was Device not found, No device detected ) fastboot fastboot mode ...right now tape into terminal :
# ./fastboot flash bootloader bootloader.img
...you will see that copy something
# ./fastboot flash boot boot.img
..you will see that copy something
# ./fastboot flash recovery recovery.img
...you will see that copy something
- now you can go into recovery to flash your favorite system....100% works !!!
A : ( attention! you do not need to touch any key in your device : just open Ubuntu....and in terminal comm write :
>$ sudo su
passw : ( write your password)
># java -jar UnBrickableResurrectorR40.jar
- Select "S5PC110 (Nexus S)"
- connect USB cable
- put the battery back
and wait ....after a few seconds you will see img. UnBrickable changed , now follow the above instructions ..(B)....).
Good luck ! for me it works very nice !
If this does not work , you have only solutions : remove the battery from your phone , and leave it two or three days , than you can go to (A) than (B)
surdu_petru said:
OK!
B : try again ...and wait for image UnBrickable to change..than press ...Downloade Mode ...... you'll see ( where it was Device not found, No device detected ) fastboot fastboot mode ...right now tape into terminal :
# ./fastboot flash bootloader bootloader.img
...you will see that copy something
# ./fastboot flash boot boot.img
..you will see that copy something
# ./fastboot flash recovery recovery.img
...you will see that copy something
- now you can go into recovery to flash your favorite system....100% works !!!
A : ( attention! you do not need to touch any key in your device : just open Ubuntu....and in terminal comm write :
>$ sudo su
passw : ( write your password)
># java -jar UnBrickableResurrectorR40.jar
- Select "S5PC110 (Nexus S)"
- connect USB cable
- put the battery back
and wait ....after a few seconds you will see img. UnBrickable changed , now follow the above instructions ..(B)....).
Good luck ! for me it works very nice !
If this does not work , you have only solutions : remove the battery from your phone , and leave it two or three days , than you can go to (A) than (B)
Click to expand...
Click to collapse
I used 'flash bootloader' earlier also, it is not flashing. Giving some write failed error. That is my problem.
I've had the same thing happen... no matter what degree of flashing, which steps taken, NONE of the so called 100% working fixes take... phone gets stuck and hangs in the google bootloader screen.... NO RECOVERY AT ALL....
All the packs and ODIN techniques over the web seem to fail and NOTHING else but the proper files seem to be the last hope...
Once in awhile, one can get into fastboot... but any attempts to load recovery directly land flat and hard back on the google boot screen and don't budge... it's like the fastboot flash operations never happened... or some other error of enigmatic mystery thwart all attempts to get this rather expensive paperweight to revive...
There's gotta be some way to fix this!!
Anyone? please and thanks!
I thought there might be a few people who have Macs with questions who'd like to get a quick express guide to getting up and running with Ubuntu Touch on their phone. This isn't that different than flashing your ROM and in fact is the same procedure on linux or windows except the adb and fastboot bins come from somewhere else.
* If you don't already have it, install ADB and Fastboot
http://code.google.com/p/adb-fastboot-install/
* Download the five images files for your device from Ubuntu
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
CODENAMES
Galaxy Nexus - maguro
Nexus 4 - mako
Nexus 7 - grouper
Nexus 10 - manta
quantal-preinstalled-boot-armel+CODENAME.img
quantal-preinstalled-recovery-armel+CODENAME.img
quantal-preinstalled-system-armel+CODENAME.img
quantal-preinstalled-armel+CODENAME.img
All Phones need this main image
quantal-preinstalled-phablet-armhf.img
* Plug in your phone and open a terminal to the folder where you saved the images. Unlock your phone if it's not already.
Code:
fastboot oem unlock
* Power your device down and enter fastboot by holding both volume buttons and the power button until the phone comes on.
* In fastboot, enter the following commands in the terminal:
Be sure to replace CODENAME with your device's code name.
Code:
fastboot flash recovery recovery-quantal-preinstalled-armel+CODENAME.img
fastboot flash system quantal-preinstalled-system-armel+CODENAME.img
fastboot flash boot quantal-preinstalled-boot-armel+CODENAME.img
* Use the volume keys to choose recovery and press the power button
* Enter the following command in the terminal:
Code:
adb sideload quantal-preinstalled-armel+CODENAME.zip
Wait for the sideload to finish.
If you see the message “fixing fs_size in crypto footer”, it’s finished.
From the main menu choose "Advanced" and "Reboot" to recovery.
When the phone has rebooted back to recovery, execute the following command in the terminal:
Code:
adb sideload quantal-preinstalled-phablet-armhf.zip”
When the sideload is finished, restart the device.
Now you're running Ubuntu.
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
TingTingin said:
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
Click to expand...
Click to collapse
There should be no reason why not (Same with Linux)
TingTingin said:
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
Click to expand...
Click to collapse
yes. they are the same instructions on linux, mac, and windows
Pirateghost said:
yes. they are the same instructions on linux, mac, and windows
Click to expand...
Click to collapse
I did mention that
- Nexus 4 / PA 3 / Franco r83 -
Hmm... I keep getting an error when trying to load the recovery. Weird since the other 2 work. Let me check the MD5Sum. I'm on Windows.
EDIT: Fixed: I just used this link and followed the instructions here. http://liliputing.com/2013/02/how-t...h-on-a-nexus-7-with-windows-mac-or-linux.html I didn't really know what was going on with your instructions. =.3 I'm sorry.
can you show some photo for your operating...i'm very interesting..............
Thank you so much, I did it with linux. Just add a couple of things;
To fastboot mode you just need volum down botton.
I had error with adb sideload (never before flashing android roms), but I solve executing "adb usb" just before adb sideload, in both cases (maybe is a problem with the last recovery...)
I also got the error: closed message
To fix first do ADB Devices to ensure that your system in online then in the recovery screen on your device select 'INSTALL ZIP FROM SIDELOAD' and reexecute the command in terminal
how to use galaxy s3 mini ? it's not fastboot mode
For all, who have a brick.
To solve the problem, you should do next:
1. Download the original file of firmware.
2. Get out from the archives the BLOB file.
3. Put it in the directory with adb and fastboot.
Next, there are few solutions to the problem.
The first way:
1. Boot into recovery or bootloader (if you can)
2. If you can't boot into bootloader, boot in it with command
Code:
adb reboot bootloader
3. Now you should install firmware. When you are in BOOTLOADER you can do this command
Code:
fastboot -i 0x0b05 flash staging blob
Now, even after command line say @ok, DON'T reboot your tablet. You must wait until you see progressbar on the screen and in will be 100%.
4. Next you shoul flash recovery. DOWNLOAD Flash it with command
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
after that you will see msgs like "sending..." and "writing.." wait about 10 minutes after last msg. And reboot your tablet in bootloader with VOLUME DOWN + POWER
5. See in recovery if partitions are mounted and have or not zero sized internal memory.
Thats all. GL. Maby write smth else in this thread.
do you mean 100% written within the progress bar ?, cuz all i have is a filled progressbar with nothing within it , i've been waiting for about 10 mins , how long does it usually take ?
ningen90 said:
do you mean 100% written within the progress bar ?, cuz all i have is a filled progressbar with nothing within it , i've been waiting for about 10 mins , how long does it usually take ?
Click to expand...
Click to collapse
if you have fully filled progressbag - that's i mean 100%
it's good and ok
do next steps.
aLkRicha said:
For all, who have a brick.
To solve the problem, you should do next:
1. Download the original file of firmware.
2. Get out from the archives the BLOB file.
3. Put it in the directory with adb and fastboot.
Next, there are few solutions to the problem.
The first way:
1. Boot into recovery or bootloader (if you can)
2. If you can't boot into bootloader, boot in it with command
Code:
adb reboot bootloader
3. Now you should install firmware. When you are in BOOTLOADER you can do this command
Code:
fastboot -i 0x0b05 flash staging blob
Now, even after command line say @ok, DON'T reboot your tablet. You must wait until you see progressbar on the screen and in will be 100%.
4. Next you shoul flash recovery. DOWNLOADFlash it with command
Code:
fastboot -i 0x0b05 flash recovery twrp.blob
after that you will see msgs like "sending..." and "writing.." wait about 10 minutes after last msg. And reboot your tablet in bootloader with VOLUME DOWN + POWER
5. See in recovery if partitions are mounted and have or not zero sized internal memory.
Thats all. GL. Maby write smth else in this thread.
Click to expand...
Click to collapse
This should really be in the general section. Still a good find though.
Sent from my SGH-T999 using Tapatalk 2
aLkRicha said:
if you have fully filled progressbag - that's i mean 100%
it's good and ok
do next steps.
Click to expand...
Click to collapse
On my bootloader there is no USB icon there are only 3 icons,,,,it is jb 4.2.1 boot loader,,,,i am running energy 4.2.1 themed rom....what to do now??
jaffer707 said:
On my bootloader there is no USB icon there are only 3 icons,,,,it is jb 4.2.1 boot loader,,,,i am running energy 4.2.1 themed rom....what to do now??
Click to expand...
Click to collapse
i also haven't USB icon. It's normal, go to the next steps.
still bootlooping , same thing as yesterday , twrp recovery is working , all the partition and data are there , tried restoring my Nand backup ,again ! , bootlooping.
everything was working fine before , except for some of the sensors, (only affected some games like temple run 2 ) , so i said "hey , i have some free time , let's revert back to stock to see if i can get those sensors back on, WHAT COULD GO WRONG ! " , and here i am, wasted a day and a half trying to fix it , and now i'm really tempted to buy a sledgehammer. anyways thanks for your help : ) , you've been more helpful than others.
jaffer707 said:
On my bootloader there is no USB icon there are only 3 icons,,,,it is jb 4.2.1 boot loader,,,,i am running energy 4.2.1 themed rom....what to do now??
Click to expand...
Click to collapse
Fastboot protocol will start automatically when you connect your TF300 to your pc through usb cable when in bootloader :good: its the property of 4.2 bootloader
ningen90 said:
still bootlooping , same thing as yesterday , twrp recovery is working , all the partition and data are there , tried restoring my Nand backup ,again ! , bootlooping.
everything was working fine before , except for some of the sensors, (only affected some games like temple run 2 ) , so i said "hey , i have some free time , let's revert back to stock to see if i can get those sensors back on, WHAT COULD GO WRONG ! " , and here i am, wasted a day and a half trying to fix it , and now i'm really tempted to buy a sledgehammer. anyways thanks for your help : ) , you've been more helpful than others.
Click to expand...
Click to collapse
so.. if all your partitions are working now, why you don't flash rom from recovery. and did you do HARD formating of all partitions??
Ti2 said:
Fastboot protocol will start automatically when you connect your TF300 to your pc through usb cable when in bootloader :good: its the property of 4.2 bootloader
Click to expand...
Click to collapse
That's right!
aLkRicha said:
so.. if all your partitions are working now, why you don't flash rom from recovery. and did you do HARD formating of all partitions??
Click to expand...
Click to collapse
i did try that , tried flashing cm 10.1 , tried restoring my previous Nandbackup , nothing , with those custom roms , the tab doesnt go beyond the boot screen (with nividia logo) , with the official firmware it goes beyond that to the silver asus logo and the rotating circle
ningen90 said:
i did try that , tried flashing cm 10.1 , tried restoring my previous Nandbackup , nothing , with those custom roms , the tab doesnt go beyond the boot screen (with nividia logo) , with the official firmware it goes beyond that to the silver asus logo and the rotating circle
Click to expand...
Click to collapse
and what is after roating sircle? Try to do all points from the 1st post.
nothing , it's been stuck on this screen for more than half an hour , i did all the steps exactly like the first post(which i already did yesterday , but i did it again anyway ). btw on the boot screen , in the upper left corner , it says "keydriver is not found , booting os " what does it mean ?
ningen90 said:
nothing , it's been stuck on this screen for more than half an hour , i did all the steps exactly like the first post(which i already did yesterday , but i did it again anyway ). btw on the boot screen , in the upper left corner , it says "keydriver is not found , booting os " what does it mean ?
Click to expand...
Click to collapse
khm... try this:
go in recovery, run adb. paste
Code:
adb shell
next, if this command is successful paste
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
and
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and go on 1st post. if it's good it is good if not.. go to the recovery and download in in your adb folder. Perform 4 and 5 or 6 points, and perform 1st post
after give it
Code:
fastboot reboot
, in the terminal i have this response
Code:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
and tablet is freeze. Any solution ?
it booted , IT BOOTED !!!!!!!!!!!!!!
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
i'm not sure why , but apparently it's related to root , whenever i tried to reboot from recovery ,it would ask me if i want to install superSU but i always chose to not install it , this try i decided to install it , and Viola ! , it booted
ningen90 said:
it booted , IT BOOTED !!!!!!!!!!!!!!
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
i'm not sure why , but apparently it's related to root , whenever i tried to reboot from recovery ,it would ask me if i want to install superSU but i always chose to not install it , this try i decided to install it , and Viola ! , it booted
Click to expand...
Click to collapse
If i help you, i am happy for you :highfive:
riderskull said:
after give it
Code:
fastboot reboot
, in the terminal i have this response
Code:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
and tablet is freeze. Any solution ?
Click to expand...
Click to collapse
i don't tell you do this comman. Wait for progress bar
thank you very much ! , (though the commands and executable didn't exactly work. adb isn't properly installed, so it's on my end ) but nonetheless , thanks , i probably wouldn't have done it if i weren't on this thread , btw , will be safe to flash a custom rom now ? , the last 2 days were excruciating , so i just want to be sure. are custom roms compatible with the new bootloader ? , i now this probably should be asked in the specific rom thread , but hey ! , it never hurts to ask
ningen90 said:
thank you very much ! , (though the commands and executable didn't exactly work. adb isn't properly installed, so it's on my end ) but nonetheless , thanks , i probably wouldn't have done it if i weren't on this thread , btw , will be safe to flash a custom rom now ? , the last 2 days were excruciating , so i just want to be sure. are custom roms compatible with the new bootloader ? , i now this probably should be asked in the specific rom thread , but hey ! , it never hurts to ask
Click to expand...
Click to collapse
I dont know. I try to flash DEODEX rom, but it isnt started.. custom roms i dont try to flash. So, i decidet to stay on the original firmware with root.
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 all!
First of all, Im new here, sorry if this is in wrong section (please don't delete the thread, move it to other section if needed) and that this has been posted millions of times but Im in really really dire need of help, and people told me this is best place to come to!
So here it is, I've tried countless methods and read alot of threads all over internet and nothing seem to work for me. (All info is down below just read it )
I tried with ADB and Fastboot, but where I get stuck always is with that my phone, somehow rejects new recoveries (TWRP, CWM) (???). What I mean is that when I try to start phone in a custom recovery(either holding +-volume and power button , or volume + and power or volume - and power) I get nothing(I can get him into his own recovery, but only options are to reset, shutdown and update and recovery and that is from first holding -volume and power then from fastboot and rescue mode and then by holding +volume). I got him ONCE to recovery(or whatever/however that place is called) where I can wipe partition cache and dalvik , it just stays at Huawei logo.
I tried both with scripts and with manual way where I input commands in cmd. I've bricked my phone about 4-5 times , and I know how to unbrick it with ease. What I dont know is how to get phone to take a custom recovery. And yes, I have unlocked BootLoader and followed all and every step there was in each guide I found. I tried with the most hated method (KingRoot and other kinds) but nothing.
Info you might need:
-As stated, phone is p8 lite, with marshmallow 6.0. (ALE-L21C432B584)
-BootLoader unlocked.
-I have all necessary drivers installed and all permissions on my computer for drivers to work correctly.
-Kernel Version - 3.10.86-gd9a2b44
-Yes of course I have debugging enabled everytime.
Once again, methods I have tried:
-ADB and FlashBoot
-All kinds of programs through phone (Kingroot, Iroot, KingOroot etc.. (I read that you can't root phone through this method but gave it a shot.))
-I don't remember if there was any other method to do it tbh because Ive been doing it for last 2 days and Im kinda tired and super pissed hehe.
But if I forgot/missed something of information that you need please just ask.
Sorry if there is too much of detail, I just wanted to describe my problem as perfectly as possible and as in much detail as needed.
Thank you all who will read/read (Oh the typing world) my thread I really appreciate your time and effort. All and any help regarding my problem will be tried out and appreciated ^^!
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
keikari said:
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
Click to expand...
Click to collapse
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Ebilog said:
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Click to expand...
Click to collapse
Weird, though you must have done something wrong when installing TWRP, because it removes stock recovery. Make sure you have typed everything right. Because if you type like "flash recvery" insted of "flash recovery" it shows stuff that by quick glance might seem correct. Oh I forgot you need root to reboot with terminal emulator XD mb. Could you show what fastboot shows when you install TWRP.
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Ebilog said:
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Click to expand...
Click to collapse
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
keikari said:
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
Click to expand...
Click to collapse
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Ebilog said:
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Click to expand...
Click to collapse
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
keikari said:
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Ebilog said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Click to expand...
Click to collapse
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
keikari said:
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
Click to expand...
Click to collapse
So i managed somehow to get the to twrp menu and i flashed supersu and i flashed new version of twrp . but i think thats what made it crash. Would it be ok if my phone stayed with 3.0.2.0 ver instead of getting 3.1.0.0?
Bcoz when i flashed 3.1.0.0 phone got stuck on 2nd logo and didnt reset or anything.
Thank god i know how to unbrick a phone at least hahahah
Edit: If this thread stays and people with problem like mine need help , feel free to pm me ill gladly help
yeah older TWRP is good if it works.
Though problems you got are still weird.
I had this problem ..
If you have restored your system and can access twrp recovery , download supersu v2.62 and install it .. this version worked for me after trying many ..
Every time my phone bricks i was downloading new whole system , instead try flashing it with twrp its better ..
Good luck .