Related
Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.
This means you are on the leaked version now and there is nothing that can be done as of right now.
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.
sounds like you got a bad pb001.img file.
ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?
nevermind addressed my issue
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.
af man...seriously!
out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!
Hi fellow streak users. Hopefully I'm asking questions in the right place.
Background:
I have read a fair amount of threads on upgrading the streak. I had 1.6, GUASBA111100 (build 6267? from memory), and received the dell 2.2 update notification. Downloaded the update and selected it when it downloaded. The phone re-booted, then sat at a black screen. There it sat for many hours. I tried re-downloading the update many times, but it does the same thing.
I got sick of this and started digging on the web. A simple method seemed to be to rename the file Update.pkg and put it on the root of the sdcard. It then sits at the dell logo. Forever. I have downloaded more images, roms, recoveries than I want to admit. I have attempted following fastboot instructions. They all fail on the reboot.
Currently the phone will not start up at all. Is it really possible to brick the phone?
What I'm trying to do.
Given all the bad publicity I have read about the current 2.2 from dell, I am hoping to install steve's latest version. I am hoping someone has some time and patience to explain how to do this. (commands and which files to use) (as the phone does not seem to respond to all the methods flooding multiple forums).
If you need further information, please ask.
Try flashing the stock recovery for the 1.6 build you have then it should boot as normal. Make sure all the other versions you have are not in the "fastboot" c:/ folder.
OK, here's the update. It's a bit jumbled and random, but I have been up for at least 18 hours fiddling...
I was unable to find the stock recovery for the 1.6 build I had. Probably lots of mismatched files were flashed unnecessarily. Nothing would touch the 'carrier unlocked US version' I had. That is until I tried QDL tool upgrade M 2.7.4.8 Now I suspect it is a beta version of 2.2 that it puts on the phone. It's slow and featureless. But it was the only thing that worked. From there I managed to make clockwork recovery work, and worked my way from steve's 1.4.6 to 1.5.1 to 1.5.2 Somewhere here the phone chucked a spaz and I discovered my phone had been booted off the network (showed no signal coverage). I began to suspect something to do with the imei being blocked (Another streak I was playing with is locked to O2, but came with a rebelsim installed - apparently illegal in australia). I checked the IMEI and it had mysteriously changed. (I suspect it had somehow been put to all zeroes, and something somewhere had given it a 'different' one.) Anyway, I used the QDL tool again, and the original one came back.
Finally what worked for me: QDL tool to flash 2.2, flashthe new amss.mbn, flash clockwork recovery, put steves 1.4.6 on SDcard and flash, then flash 1.5.3
(I couldn't tell you where I downloaded the files that worked. Your results (people who are still seeking action to try and upgrade their software) may vary. All I can say is that now I have downloaded half the internet and installed all the computer drivers, I have hit on a combination that works for me on this computer).
Steve, Thankyou! It's fast, snappy. It has those settings I love to twiddle.
Thank you to everyone else that has either directly or indirectly helped me with your description of how you got yours working.
Thank you for the hosting of the ROMS. I like that you don't have to wait 45 seconds and/or join to download.
A few comments:
I downloaded so many roms and files that it wasn't funny. The problem is that they are all named Update.zip, amss.mbn etc. When they are all in the download folder... Some people just provided the files, others packaged them with a batch file to automate the process. If I was to download them all again, I would download them into folders labelling them...
There seems to be a wide variety of situations/variables that dictate 'what you need to do and how you need to do it' to change roms in the phone. There are half a dozen comprehensive guides on the net, yet all different. I was quite confused. It almost needs some sort of chart where you can pick where you are at the moment, where you want to be, then follow those instructions.
I was also bamboozled with the different tools. QDL, flashboot, ADB etc. I have a bit of an idea, but I'm sure others are equally confused. I know the information is 'out there' but to have it all in one place. What do some of the files do. Why might you need to flash them. Which files are erased by the stock ROM if you don't do anything with them. What does it do when you flash a recovery? How long does it stay on the phone?
There are several parts of the phone that get upgraded. Not sure I have it right, but QDLtool upgrades the modem software (amongst other things) Other things you change is the baseband, SDcard contents etc. (Trying to connect what software files go to what places to what hardware in the phone.)
I do have several questions that have arisen.
1. Am I right in thinking you must flash steves 1.4.6 before you can flash the latest 1.5.3?
2. QDLtools: In theory is it possible to replace the files somehow so it puts steve's latest ROM straight on?
3. Rebelsim: (The small amount of information I have suggests it is illegal in australia) Does it block or change the imei? Can the carrier tell if you are using one?? (not that I use one, apparently they don't work on 2.2)
(that's all for the moment.)
i have been having problems with doing my streak aswell and still am but
ato answer one of your questions that i found out while downloading the whole internet is that the QDL tool can be used to put steves on
here is the instructions i just copied off the qdl page i would of posted a link but i am a new member so i cant post inks yet
Beyond QDLTool
Using QDLTool will get you to a pre-release of v2.2. From here, you’ll want to upgrade to a newer release. The two options that people tend to choose from are to either go up to the official v2.2 ROM from Dell, or install DJ_Steve’s latest ROM.
Official ROM
If you want to go to the latest official ROM from Dell, simply set up your wifi connection, then go to Settings -> About Phone -> System updates. The latest update can then be downloaded and installed, updating your Streak.
Latest Streakdroid ROM
If you want to upgrade to the latest Streakdroid ROM (1.5.3), either from the QDLTool install or from the latest official build, you can follow these steps:
1.Go to the downloads section and grab StreakMod Recovery, the latest 1.5.3 Update and the AMSS for 1.5.1+ (the update and amss are under Roms, StreakMod Recovery is under Recovery)
2.Copy the update-1.5.3.zip file onto the root of your SD card.
3.Extract recovery.img from the StreakMod recovery and place it, along with amss.mbn, into the same directory as QDLTool (QDLTool has a copy of fastboot)
4.Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
5.The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
6.Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
7.Open a command window and use ‘cd’ to change to the same directory as qdltool.
8.Run: fastboot -i 0x413c flash recovery recovery.img
9.Run: fastboot -i 0x413c flash amss amss.mbn
10.Run: fastboot -i 0x413c reboot
11.As the Streak starts to reboot, hold down both volume buttons.
12.The recovery menu should come up; select option 2 (Upgrade)
13.A Dell logo and an exclamation mark should appear; press power or menu to open StreakMod’s main menu
14.Select ‘apply sdcard:update.zip’ then ‘chose zip on sd card’
15.Find the update-1.5.3.zip file, select it and apply the zip.
16.When the update finishes, press back a couple of times then select the option to reboot your Streak.
17.The Streak will restart. It will take about 5 minutes to complete, but you are now on the latest v1.5.3
at moment i am following the qdl guide to getting the steve rom on my phone so will let you know how it has gone but with that guide the installation at moment seemed seemless now got to see if it goes off the dell logo after a while if not got to recovery but lets hope
no luck so far
stuck on the logo screen but asked for help now its a waiting game
Cheers for that!
Sent from my Dell Streak using XDA App
Is it necessary to use QDLTool to get to the pre-release 2.2 if I am on 1.6 or can I just follow steps 1-17?
The reason I ask is that QDLTool for me just stops at "Check version ... " so I have not been able to complete running it.
i dont know if it is necessary
are all the drivers installed?
i used to have a prob where it kept failing me but all i had to do was change usb port
and got it working but i was running 2.1 stock at the time but that was buggy and crap UI
have you tried just puting 2.1 or 2.2 on your SD card and updating that way
i finally got my streak sorted
i started from scratch
first i installed clockwork mod using fastboot
then installed very version of steves roms in order starting with 1.1.1
and worked my way down and when i installed 1.5.0 i then ran flashed the amss that is required if you want to get the newer versions then installed the rest of the updates and when i got to 1.5.3 i also installed the camera fix
i found it best to put all steves rom zip files onto your SD card at once then it saves having to keep putting one of after another
also after every update leave the phone for a few mins because it does take a lil time to sort the updates out
THE ROM UPDATES (at top also has the AMSS that need flashing)
http://streakdroid.com/?page_id=15&category=1
Camera fix and the comandlines for the AMSS update
http://forum.xda-developers.com/showthread.php?t=802405
clockwork
http://streakdroid.com/?page_id=15&did=9
I don't know if all the drivers are installed. Is there a way to check? I cannot even get into FASTBOOT (POWER + CAMERA) mode and the Streak is just in an infinite reset loop.
Just a note, the older StreakFlash QDLTool completes completely but the newer one in Repairtool just sits infinitely at "Check Version ... "
what operating system you using on your computer
rahbone said:
what operating system you using on your computer
Click to expand...
Click to collapse
Nice of you to ask, as indirectly that was the issue. I outlined it over at the forum mydellmini dot com. Sorry, cannot post hyperlinks as yet. Issue has been resolved. Looking now to load 1.5.3
why not spam a few more posts on here then u can do links when u want 2 in future
you just need 3 more posts i believe the you can do links
Like a regular common or garden dumbass I updated my O2 streak using a rebel simcard to froyo today, forgetting that the rebelsim might not work.....which it doesn't of course.
So I tried downgrading to 1.6 again but I just cant get it to work! I've tried loads of stock roms from various places (4399 and 3833) and loads of recovery images including stock, clockwork and streakmod but I get different errors everytime.
Firstly I get told it cant be verified, then it wont recognise the sdcard at all, then it tells me the update.zip is "bad", and when I do get one to install it won't load past the dell logo.
I'm certainly no retard when it comes to this sort of stuff, but its all rather new to me nonetheless. I understand what recovery image you need depends on what rom your trying to install? I've tried countless recommendations from all over the internet, none of which seem to work.
Any idea's greatly appreciated as im completely stumped. I figure if I could get hold of the current o2 2.2 rom then I might be able to get that to work using the current recovery image (which i have got). Doesn't solve my rebelsim problem of course, but at least it would boot!
Like I said, would greatly appreciate some help!
http://forum.pocketables.net/showthread.php?t=8221
Thanks a lot for the link, thought I was sorted but I think thats a dell 2.2 build rather than one that will work on O2 as when it tries to install the update.zip it says it cannot be verified. I can't think what else it would be anyway.
Anyone know where I can get hold of an O2 2.2 rom?
Tried using the rom found here using the 2.2 recovery
http://www.streaksmart.com/2010/12/...0c#comment-6a00d83451c9ec69e20148c6d068d0970c
But now it tells me assert failed: getprop("ro.product.fota.model")
Sigh
Valandil3 said:
Tried using the rom found here using the 2.2 recovery
http://www.streaksmart.com/2010/12/...0c#comment-6a00d83451c9ec69e20148c6d068d0970c
But now it tells me assert failed: getprop("ro.product.fota.model")
Sigh
Click to expand...
Click to collapse
The fota error means you have a recovery thats not for that rom. The rom checks to make sure its flashing to whatever version of the streak it was meant for.
Put the update.pkg on the root of your SD card
Download and unzip the attached file, then flash that via fastboot
Code:
fastboot -i 0x413c flash recovery recovery.6941.img
fastboot -i 0x413c reboot
Hold both volume buttons
select option 2 and it should work
(i think this recovery is for an 02 model so hopefully it'll do the trick)
Reply here if not or just try to find the stock 02 recovery.
good luck
your an absolute legend my friend, thanks so much!
Still can't make phonecalls for the time being of course, but don't really care right now, just glad it boots again!
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
How did you tried connecting phone to odin? Did you went into download mode then connected the phone to pc ?
DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
The rom you mentioned is a banned rom
You have 2 options
Option 1
If you can get into recovery mode (Vol up home button power button)
Download any stock based custom rom
Go into cwm
Format system data cache
Mount system data cache
Flash rom zip
Assuming that you are using a stock based kernel it will boot
Option 2
Flash stock rom via odin
See my firmware thread link in my signature
Note you can use standard 5360 firmware instead of the b variant which may be better
Posting to say I didn't get the phone to work still, but I got home without too much trouble. needless to say this thread is no longer an emergency.
I want to express my gratitude to you guys for helping me out, thank you so very much.
Unfortunately as I say the phone does still not work -
With multiple attempts using ODIN I keep getting the hangup at 'setup connection' - I tried on mac via parallels (windows 7) and a windows 8 machine.
I can successfully install a ROM via CWM but the phone gets stuck in a boot loop (samsung galaxy y splash screen) so I'm guessing I have a kernel problem? When I try flashing a new kernel I get the "error mounting /sd-ext!" message, and the same when I try to format it via CWM. I found this: http://forum.xda-developers.com/showthread.php?t=1750888, but I cannot boot the phone so I guess I'm stuck.
My last install attempt was these
http://forum.xda-developers.com/showthread.php?t=2462914 - V3LenoxEvolution ---- SUCCESSFUL INSTALL.
http://forum.xda-developers.com/showthread.php?t=2644262 - Blackheart kernel ---- FAILED, error mounting /sd-ext
Got any other ideas guys? Or do you know where I'm going wrong?
I think I'm in way over my head :s
Many thanks once again!
EDIT: some additional information, I cannot reboot to bootloader, and as far as I can tell I can't replace the custom recovery CWM v6 (I find a different version, boot into CWM v6, click install .zip from sd card and say CWM v5 launches, but when I reboot it's back to v6)
Flash stock rom via odin....
Flashing other diffrent ROM packages won't help until you have right bootable kernel...
So put your efforts towards making it to boot up on a stock firmware....
By ODIN mode
Try installing drivers and checking that no other device is connected to pc via USB.
Also make sure you follow the guide properly....
Then post errors ...or try google...
We'll help...
Sent from my GT-S5360 using XDA Free mobile app
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and when the device reboots it then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
MarkAllen said:
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and it the device reboots then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
Click to expand...
Click to collapse
From what i recall the fingerprint is what is shown in the buildprop. You could try editing this but i would tread carefully if its just a minor update as it may justmess up your system if there are other mismatches during the update process.
Lenovo technical support is a complete joke, you get much better help here. Lol
Sent from my F5121 using Tapatalk
Nope every line of my build.prop, where listed, has the proper "Lenovo/yeti_10_row_wifi" that the update claims is wrong. I personally think it is this update itself but no confirmation from other users if the update
"YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90 F_USR_S000426_1705080316_WW06_BP_ROW"
has installed for them yet.
And I certainly knew how far I was *not* going to get with Lenovo but figured it couldn't hurt. I was really trying to get a stock ROM download from them or anywhere. I would love to just revert this to how it was out of the box and start over.
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
MarkAllen said:
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
Click to expand...
Click to collapse
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Broomfundel said:
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Click to expand...
Click to collapse
Thanks for that confirmation! I did end up getting a registered account ($15) used Paypal and all looked good. I ended up downloading two versions of firmware. Initially I thought I would start with the oldest knowing many updates awaited but really wanted to be sure in erasing all my previous steps just in case it didn't work or the same thing happened again.
Used "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" from Easy Firmware. I opted to follow the included "installer.cmd" but did not do the "unlock" or "lock" as I already was unlocked of course and did not want to lock it again. When it completed I first noted my Halo keyboard not working and things were in Chinese here and there. This post resolved both items (thanks vimalbhimani!). Pretty sure that was because I formatted all the various partitions including "country", duh. Sadly however this version was showing no further OTA updates were available at all. Maybe Lenovo has deleted some of the really old OTA downloads and they are no longer available? Not sure.
I then installed the most recent rom "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". This time I did not format and only flashed this newer roms boot, bootloader, factory, recovery, and system images. After the system was backup everything was in great shape and updates were available. I made a TWRP backup straight away. Then I let the first and second updates listed below download and install via OTA and had no issues. The final two I opted to save time and installed using the standard recovery from my SD card after I downloaded them from my PC. Here are direct links to those if anyone wants them and they are in order of install (descending) based on already having "YB1-X90F_USR_S000196_161104"
http://tabdl.ota.lenovomm.com/dls/v...S000239_1612091428_WW06_BP_ROW_WCAC703BC6.zip
http://tabdl.ota.lenovomm.com/dls/v...S000340_1702251540_WW06_BP_ROW_WC365253B3.zip
http://tabdl.ota.lenovomm.com/dls/v6/YB1-X90F_170420_WC76FD00EF.zip
http://tabdl.ota.lenovomm.com/dls/v...S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip (this is the failed update that incited this thread)
All updates went great and all is well at this point. Made another TWRP backup and I plan to root again now and see if any upcoming updates later have some issue?
I just wanted to report back here if anyone was interested that I unrooted, updated the June OTA update, and was able to root again without issue.
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
FreddeHamm said:
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
Click to expand...
Click to collapse
You cannot flash the ZIP file with TWRP or stock recovery. You have to unzip the file and then flash each IMG file that you need manually while in fastboot mode (there are seven of them).
**** IF YOU FOLLOW THESE DIRECTIONS IT IS NO ONES FAULT BUT YOUR OWN IF IT SCREWS UP SOMETHING!!! ****
**** WILL TRY TO HELP PROVIDE INFO IF I CAN BUT CANNOT GUARANTEE ANYTHING. ALSO THIS ERASE ALL YOUR DATA ****
First be aware as noted in the previous post above that I tried using "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" intially and it worked fine to get me back up and running but once I was done no new OTA updates were showing at all. No clue why so I ended up doing it again but used the ROM named "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". Also note I had erased my "country" partition and flashed "country.img" which requires the info posted by vimalbhimani again linked above in my previous post. It has to be used to correct for your country, no biggie at all and worked fine for myself.
1) Unzip the ROM you downloaded to a folder on your PC
2) From command prompt go to that folder
3) Make sure from the command prompt that ADB and fastboot commands are working properly
4) Put your tablet in fastboot mode ("adb reboot bootloader")
(these next commands are directly from the "install.cmd" included with the ROM from EasyFW, I just opted to run them manually one at a time in order and I omitted the unlock and lock commands)
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot continue
That's it. Minus the Intel error code 03 for being unlocked, it should be a normal out of the box setup when it boots back up into Android.
good luck!
People that are looking for the YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip may want to take a look at this post.
In contrast to my experiences with devices made by other OEMs, it seems like the files can directly be used for downgrading the Yoga Book if you're currently using a newer version.
Moved...