I am using a Nexus 5, and I tried to flash the CyanogenMod 11s from OnePlus One to my Nexus following instructions from here:
http://www.ibtimes.co.uk/nexus-5-gets-port-cyanogenmod-11s-featuring-android-4-4-4-1458608
My phone was not rooted, I performed a root and apparently succeeded, because I saw SuperSU installed on my device. I then proceeded to follow the instructions from the site mentioned above, performed a factory reset, and selected the ROM I downloaded to flash. The flashing failed and I am currently stuck in bootloop, afraid to proceed further and brick my phone.
Some of the signs I noted with my phone:
At the ROM installation screen, it says 'checking for MD5 file... Skipping MD5 check: No MD5 file found', 'symlink: some symlinks failed', ' E: Error executing updater binary in zip '/sdcar', and 'Error flashing zip '/sdcard/CyanogenMod_11S_ham'
At Reboot menu, upon tapping on 'Recovery' option it says 'No OS installed! Are you sure you wish to reboot?'
Please help me out, I'm sick at the moment, guess it is not a good idea to flash a ROM when you're sick huh? Been trying to find a solution and can't seem to find it, not sure if because I'm sick and too tired to read through or there really isn't a situation like this...
Thank you!
first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it. second option, flash the factory img via fastboot while youre in the bootloader. it has nothing to do with being sick, it has everything to do about learning all about your device and how to take care of it, before you start modding your device.
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
I build my own ROM even when I'm sick, what do you mean?
Try redownloading as it had flashing issues before
jackhayden said:
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
Click to expand...
Click to collapse
no, you didnt actually. you could have had a bad download, that happens often enough(but i dont think its the case, as it wouldnt remove your rom), you also could have experienced a recovery bug, that also can happen from time to time. btw, did you mention which recovery youre using?
I'm using TWRP.
jackhayden said:
I'm using TWRP.
Click to expand...
Click to collapse
well, try to download it again, and push it to your drvice with adb, then reflash it. or try pushing another rom. or, you always have the failsafe of flashing the factory img. btw, did you happen to make a backup in recovery before you flashed? you should always make a backup in recovery if flashing something new, just in case. in your case, it would make thing extremely easy.
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
jackhayden said:
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
Click to expand...
Click to collapse
you need to bring up the ui for typing.. on my old windows computer at work, i find an empty space on the same page that adb is located on your computer, then i left click and press the shift button on that empty space, then i get a few option that pop up, and i press the option. but im using windows from like 2004-5, lol.
Wow, that's really old.
I saw one of the commands available is 'adb push 'file name', should I try that?
Sorry for the troubles!
yup. first do "adb devices" to make sure adb sees your phone.
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
jackhayden said:
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
Click to expand...
Click to collapse
is the rom zip in the same folder as adb is located? it should be if not. and did adb see your device in with adb devices?
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
jackhayden said:
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
Click to expand...
Click to collapse
hmm.. well, i dont know that error, ive never seen it
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
Flash gapps
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
"first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it."
as @Lethargy said, gapps(google apps), you need to flash them. the google apps are not open source, they are owned by google, and cm isnt allowed to add them to the rom. but you are allowed to flash them separately
Thanks a lot for all the helps given. Really appreciate them! :good:
Related
Hi all,
I recently unlocked my VZW Xoom using the OEM unlock instructions found here: http://forum.xda-developers.com/showthread.php?t=967065
I then downloaded the most recent CWM (3.025) and followed the instructions found in this thread: http://forum.xda-developers.com/showthread.php?t=1038870
I was able to write CWM to the recovery partition with no errors showing in either ADB or on the device itself. I verified the checksum of recovery.img.
What happens now is that when I reboot to recovery from ADB, the red Moto logo shows up, and at first everything looks good. At the top it says "Reading ODM fuse 1".
Then, a green Android logo with a yellow exclamation mark on it appears over a black screen. It looks like some sort of error message. I have CWM on my phone so I know this isn't what it's supposed to look like
In any case, has anyone else seen this issue (or better yet, know how to fix it)? I should point out that after a few minutes, the Xoom automatically boots into HC and works just fine.
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Jthom203 said:
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Click to expand...
Click to collapse
Hi - thanks for the response.
Yes, I've tried that, rebooted the device, rebooted the PC, tried it again, etc. Still no dice
does it still boot? if so try installing rom manager and using it to flash CWR
Sic123 said:
does it still boot? if so try installing rom manager and using it to flash CWR
Click to expand...
Click to collapse
Yep, it still boots. I've never used ROM manager, but I did happen to just download it. I'll give that a shot.
Two other things I didn't mention in the OP:
- I do not have an SD Card in the slot.
- I also didn't 'root' the phone yet with the SuperUser APK, only unlocked the bootloader. Would either of those cause the issue?
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Jthom203 said:
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Click to expand...
Click to collapse
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
volta said:
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
Click to expand...
Click to collapse
Root was the answer. Duh. I feel dumb now.
Either way, once I get to 10 posts, I can post in the dev forum thread to make it clear that root, not just OEM unlock, is required to flash CWM so that dummies like me can get things working quickly
nice, glad that you got it working.
Be sure to install Tiamat 1.31 so you can use your SD card and get full access to CWM
Rom Manager question
Has anyone found a way to allow Rom Manager to "Manage Backups"? It appears that it isn't pointing to the correct directory/ folder.
Had the same issues after installing CWM from ROM Manager - used the adb method instead and this fixed the issue. (Xoom was already rooted and OEM unlocked)
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
I've got myself (and my tablet) into a complete mess.
When I got my tablet it was already unlocked and running ICS (I think).
I decided it was time to upgrade to cyanogenmod Kit Kat.
I started with this tutorial: http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t
I flashed the custom recovery : "recovery-jb-644"
I chose "cm-10.2.0-tf700t" as I was nervous about the nightly. Something went wrong.
The tablet started but crashed after a few minutes and rebooted. I added "gapps-jb-20130813-signed" - it was worse - now the keyboard also crashed.
After that, I tried numerous things to recover it.
Now, I cant access it through the fastboot - it gives the serial number but won't push anything or flash anything.
I put the following on an sd card and tried to install from there but I get:
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
or any number of similar messages. I tried the solution here: http://forum.xda-developers.com/showthread.php?t=1235724 which worked once but not again.
My current situation:
The picture attached shows the current installation - it will boot - I have no Google Apps - and it crashes within a minute and then reboots.
I'm not a complete newbie, but I cant find a simple explanation of what to do next.
I just want the tablet to work again, I don't care anymore if its Kit Kat, ICS, Jelly Bean or Honeycomb.... I even considered Linux...
Please help.
Apparently you missed the big fat red warning on the tutorial you linked. You need to install a 10.6.1.14.x bootloader.
(And you need to make sure your recovery is compatible with that bootloader, otherwise you risk a hard brick when you wipe data).
fivaics logical
_that said:
Apparently you missed the big fat red warning on the tutorial you linked. You need to install a 10.6.1.14.x bootloader.
(And you need to make sure your recovery is compatible with that bootloader, otherwise you risk a hard brick when you wipe data).
Click to expand...
Click to collapse
OK, so I've downloaded it, but I still can't install it because of the
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
How do I get around this?
I attach a copy of the log showing what happens when I try.
ymget said:
OK, so I've downloaded it, but I still can't install it because of the
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
How do I get around this?
I attach a copy of the log showing what happens when I try.
Click to expand...
Click to collapse
According to the page you linked, you are supposed to download a blob file and flash it via fastboot:
http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t#Update_Bootloader_To_Compatible_Version
You didn't say yet in which way fastboot didn't work for you.
Hi,
Thank you for replying.
I can't do "fastboot -i 0x0B05 flash staging XX_bootloaderblob"
When I am in the CMD window, I can do fastboot devices and it see's my serial number, but as soon as I want to actually do something, it tells me the device is not available.
The same goes for any adb commands I want to do.
The only way I found of doing it is through the sideload, but now even this doesnt work.
Hi Again,
Your comment gave me an idea - I did the bootloader fastboot through the sideloader - and it worked!!!
I then added the "gapps-jb-20130813-signed" and now it is crashing on the setup wizard.... and the keyboard crashes.
Any ideas?
ymget said:
Hi Again,
Your comment gave me an idea - I did the bootloader fastboot through the sideloader - and it worked!!!
I then added the "gapps-jb-20130813-signed" and now it is crashing on the setup wizard.... and the keyboard crashes.
Any ideas?
Click to expand...
Click to collapse
Did you reboot after flashing the bootloader and before flashing gapps?
berndblb said:
Did you reboot after flashing the bootloader and before flashing gapps?
Click to expand...
Click to collapse
Yes, I had to check to make sure that the new bootloader worked and the tablet was no longer crashing before I installed the gapps.
ymget said:
Yes, I had to check to make sure that the new bootloader worked and the tablet was no longer crashing before I installed the gapps.
Click to expand...
Click to collapse
I really have no idea... I just checked - you did flash the gapps package for CM 10.2 and I assume you also checked the box "verify zip signature" in your recovery before you flashed gapps?
If not, it maybe as simple as a bad download....
berndblb said:
I really have no idea... I just checked - you did flash the gapps package for CM 10.2 and I assume you also checked the box "verify zip signature" in your recovery before you flashed gapps?
If not, it maybe as simple as a bad download....
Click to expand...
Click to collapse
You were right!! I downloaded the gapps again and now I have a perfectly working tablet.
Thank you to everyone who answered me and helped - you guys are amazing!!
ymget said:
You were right!! I downloaded the gapps again and now I have a perfectly working tablet.
Thank you to everyone who answered me and helped - you guys are amazing!!
Click to expand...
Click to collapse
:GOOD: Glad you got it working! BTW, there's a "Thanks" button for a reason
berndblb said:
:GOOD: Glad you got it working! BTW, there's a "Thanks" button for a reason
Click to expand...
Click to collapse
I know there is supposed to be one - I've read about it - but I can't find it anywhere!!!!
Found it!!!
So, I got my Photon Q today and I've already unlocked it and I was trying to install TWRP but I messed up somehow.. It still boots into the stock Android ROM and works fine but whenever I try to go into the recovery/Fastboot (Whatever it's called) I get this screen with some info text. At the bottom it says this:
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Whenever I try to flash a recovery with an app it always succeeds but I still get this screen when I try to go into the recovery. Help me.
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
arrrghhh said:
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
Click to expand...
Click to collapse
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Cwazywazy said:
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Click to expand...
Click to collapse
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
arrrghhh said:
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
Click to expand...
Click to collapse
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Cwazywazy said:
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Click to expand...
Click to collapse
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
arrrghhh said:
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
Click to expand...
Click to collapse
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Cwazywazy said:
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Click to expand...
Click to collapse
I've heard of other people complaining about this on TWRP.
You should either a) use OpenRecovery or another recovery... or b) use an older version of TWRP. I'm on 2.6.3.1 and it works _flawlessly_.
I haven't had time to update to the latest versions of TWRP to investigate this issue.
As for your CM issue, make sure you wipe (using a recovery that works haha) and also make sure you give it plenty of time to do the first boot - there is sometimes a fsck process which runs at boot and takes a lot longer than usual for the device to actually boot up.
Please help me. I can't find any solution and I can't boot into CMod.
Cwazywazy said:
Please help me. I can't find any solution and I can't boot into CMod.
Click to expand...
Click to collapse
I gave you a solution, please at least try it.
arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Oh. I didn't see that, sorry. Trying it now.
arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Cwazywazy said:
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Click to expand...
Click to collapse
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
arrrghhh said:
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
Click to expand...
Click to collapse
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Cwazywazy said:
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Click to expand...
Click to collapse
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by. I was hoping for a logcat from the CM11 failed boot.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
TWRP is failing to mount a lot of partitions, which is obviously unacceptable. I'm still not sure why the older version wouldn't work for you...
arrrghhh said:
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
Click to expand...
Click to collapse
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Cwazywazy said:
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Click to expand...
Click to collapse
OpenRecovery?
arrrghhh said:
OpenRecovery?
Click to expand...
Click to collapse
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Cwazywazy said:
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Click to expand...
Click to collapse
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
arrrghhh said:
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
Click to expand...
Click to collapse
Ugh. Not working.
It says failed to mount /whatever (Invalid argument)
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!