Okay, I just want to get back to stock, froyo 2.2.1 OTA or whatever.
I'm tired of Gingerbread, and i would really like to just use whats really stable (Froyo) but ever since i've rooted my phone and flashed other roms every time i flash a Froyo rom (doesn't matter which one) it boots the 1st time perfectly fine(DreamTeam Froyo, NexTouch3G .ect), as for any other boot after that it doesn't boot it just hangs on the mytouch 3g splash screen, or goes to a black screen where you would think the boot animation would pop up. . . .
how ever i don't have this problem with gingerbread. . . ezGingerbread to be exact. . .
is there any fix for this issue? or even a clean way to get back to complete no root stock rom?
FastBoot info:
SHAPPHIRE PVT 32A S-ON G
HBOOT-1.33.0013(SAPP31000)
CPLD-13
RADIO-2.22.28.25
Oct 21 2009, 22:33:27
:extra phone information:
C:\AndroidSDK\tools>fastboot getvar cidnum
cidnum: T-MOB010Φ₧α=
finished. total time: 0.000s
C:\AndroidSDK\tools>fastboot getvar version-main
version-main: 3.56.531.1
finished. total time: -0.000s
C:\AndroidSDK\tools>fastboot getvar cid
cid: T-MOB010Φ₧α=
finished. total time: 0.000s
C:\AndroidSDK\tools>
Did you try this ROM?
http://forum.xda-developers.com/showthread.php?t=1400621
It is Froyo (Android 2.2.3) and compatible with MT3G v1.2 / Fender (with hboot 1.33.0013, radio 2.22.28.25)
5[Strogino] said:
Did you try this ROM?
http://forum.xda-developers.com/showthread.php?t=1400621
It is Froyo (Android 2.2.3) and compatible with MT3G v1.2 / Fender (with hboot 1.33.0013, radio 2.22.28.25)
Click to expand...
Click to collapse
I'm not too sure, i believe i flashed that too and it didn't even boot. . .
GeEazy said:
I'm not too sure, i believe i flashed that too and it didn't even boot. . .
Click to expand...
Click to collapse
Very strange cause it developed for MT3G v1.2
Did you wipe data/factory reset before flashing?
You can monitor boot-process by running
Code:
adb logcat
It posts various info when phone is booting, you can see when it starts again, or something strange...
You can write log into text file then review it...
Code:
adb logcat > log.txt
5[Strogino] said:
Very strange cause it developed for MT3G v1.2
Did you wipe data/factory reset before flashing?
You can monitor boot-process by running
Code:
adb logcat
It posts various info when phone is booting, you can see when it starts again, or something strange...
You can write log into text file then review it...
Code:
adb logcat > log.txt
Click to expand...
Click to collapse
I'll be sure to try that next time i change my rom. . . . well attempt to.
Yes i do wipe, i do the superwipe, i do wipe data/factory reset, i even go into storage and mount "system, data, cache" then format boot, system, data, cache before i flash a new rom, oh and go into advance and clear the dvilk-cache.
If you want to get back to stock, there's something I've been wanting to try.
Read everything carefully before doing anything
Download this: http://db.tt/94bZmJ0R
Get your phone running a rom with root.
Install a terminal emulator.
Install rom manager.
Copy the misc.img file you downloaded to your sdcard if not already there.
Run this command:
Code:
# /data/data/com.k*rommanager/files/flash_image misc /sdcard/misc-edited.img (or whatever its called)
You should now be able to flash almost any sappimg.zip from hboot
Download and flash the stock one. link
???
Profit!
Now time for the warnings (you listened and are just reading still, right? Haven't done anything?)
This in theory (based on MY knowledge of how this works, which I don't trust and you probably shouldn't either) should work. The misc-edited.img file is the misc partition pulled from my device and then hex edited (by me, the second time I ever used a hex editor) to have a super-cid (think goldcard) and a low main version. I don't see why it wouldn't work, unless I messed up editing it.
I cannot guarantee that this will work. I can't even guarantee it wont cause a brick, but if you really want back to stock, it's worth a shot.
tvall said:
If you want to get back to stock, there's something I've been wanting to try.
Click to expand...
Click to collapse
tvall, as i understood, you edited misc.img with lower version (for RUU, that checks versions with own) and this file can used only for MT3G v1.2 ?
5[Strogino] said:
tvall, as i understood, you edited misc.img with lower version (for RUU, that checks versions with own) and this file can used only for MT3G v1.2 ?
Click to expand...
Click to collapse
Yes, and the cid is edited to be 11111111 (so you can flash any sappimg, without making a goldcard)
I'm not sure if it'll work on anything, but there shouldn't be anything stopping it from working on 32b or 32a
LOL, I'm willing to try it, not too worried about bricking because honestly i feel like my phone is already semi brick with it not letting me run any other rom besides ezGingerbread. . . i feel bullied -_- .
My only question is how can i make a copy of my current file, so if **** hits the fan i'll have a backup to swap it back afterwards .
GeEazy said:
LOL, I'm willing to try it, not too worried about bricking because honestly i feel like my phone is already semi brick with it not letting me run any other rom besides ezGingerbread. . . i feel bullied -_- .
My only question is how can i make a copy of my current file, so if **** hits the fan i'll have a backup to swap it back afterwards .
Click to expand...
Click to collapse
Code:
# dump_image misc /sdcard/misc.img
to backup your misc partition
i think dump_image is in the rom manager files.. so do this
Code:
# /data/data/com.k*rommanager/files/dump_image misc /sdcard/misc.img
note: the * is there because im too lazy to remember or type the full path. itll work as i typed, but if you have another app with a name that also fits that(very unlikely), you should type the full path
tvall said:
Code:
# dump_image misc /sdcard/misc.img
to backup your misc partition
i think dump_image is in the rom manager files.. so do this
Code:
# /data/data/com.k*rommanager/files/dump_image misc /sdcard/misc.img
Click to expand...
Click to collapse
41! . . . Cool, I'm going to give this a try next time my rom gives me a problem, or when i get another nice themed rom like NexTouch thats more updated and working right.
Pretty much my plan would be to . .
1. Unroot my Phone(Get it back to Stock)
2. Update it to the froyo 2.2.1(If its not already Froyo stock)
3. Root my phone
4. Flash the new rom(Which is a nicely themed & Stable Froyo Rom)
Related
Hi,
I want to root my G1 dev phone running android 1.6. Is the only way to do this to downgrade to 1.5 (cupcake) ? This is what all my research tells me, but most of the guides telling me this are dated from 2009 and I'm wondering if a newer method has been found since ...........
EDIT - also is there an easy way to test if I already have root access ? It's a dev phone so maybe it's enabled already.
Cheers,
Protosbyte.
get into fastboot mode, post your results
phone details
In Fastboot mode :
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
I went to the HTC developer page where they have the recovery images
(not allowed to post the link here because of spam risk)
and flashed the recovery image thinking that might give me root.
It didn't. (I tested this by typing 'root' in the terminal emulator. I
got 'permission denied.')
So currently :
Build Number : dream_devphone-userdebug 1.6 DRC83 14721 test keys
Kernel : 2.6.29-00479-g3c7df37 [email protected] #19
So - is there an easier path to rooting and flashing cyanogens stuff than
downgrading to 1.5 ?
Cheers,
Protos.
i also have an adp1 but somehow the previous owner already managed to lose root however i used the downgrade to 1.5, flashing recovery and so on method and it worked perfectly fine and was actually not really complicated.
protosbyte said:
In Fastboot mode :
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
I went to the HTC developer page where they have the recovery images
(not allowed to post the link here because of spam risk)
and flashed the recovery image thinking that might give me root.
It didn't. (I tested this by typing 'root' in the terminal emulator. I
got 'permission denied.')
So currently :
Build Number : dream_devphone-userdebug 1.6 DRC83 14721 test keys
Kernel : 2.6.29-00479-g3c7df37 [email protected] #19
So - is there an easier path to rooting and flashing cyanogens stuff than
downgrading to 1.5 ?
Cheers,
Protos.
Click to expand...
Click to collapse
First off, if you flashed the images at developer.htc.com/adp.html, then you DEFINITELY HAVE ROOT via the "su" command. HOWEVER, you must know how to use it! The "su" command will ONLY work for the "shell" user -- which means over ADB. This is for YOUR PROTECTION to keep apps from running root-nuts and wrecking your phone.
Second, your bootloader identifies itself as 0.95.0000? Or 0.95.3000? If the former, then some previous owner took the "holiday phone" update. I suggest finding the SPL thread and loading it with 0.95.3000.
Ah - thanks for that. I didn't realize that I needed to check for root access through adb.
My bootloader is definitely 0.95.0000. I will have a look for that SPL thread you mentioned and install that.
After that, to flash cyanogen's 2.1 mod is it OK to follow this guide :
(meh - can't post links. If you google "Full Update Guide - G1/Dream Firmware to CyanogenMod" it's the top link)
from the "Custom Recovery Image" paragraph ?
Thanks,
Protos.
protosbyte said:
Ah - thanks for that. I didn't realize that I needed to check for root access through adb.
My bootloader is definitely 0.95.0000. I will have a look for that SPL thread you mentioned and install that.
After that, to flash cyanogen's 2.1 mod is it OK to follow this guide :
(meh - can't post links. If you google "Full Update Guide - G1/Dream Firmware to CyanogenMod" it's the top link)
from the "Custom Recovery Image" paragraph ?
Thanks,
Protos.
Click to expand...
Click to collapse
If you are wanting to install 2.1/cm, I suggest using this approach (which works with standard partition layouts -- be sure to read the whole thread for current versions of CM): http://forum.xda-developers.com/showthread.php?t=692614
If you really want to go follow the directions and install the deathSPL, then you DO NOT follow the CM directions -- they are DANGEROUS.
You locate and install SPL 1.33.2003 (ends in a "THREE", but not the HACKED version) using recovery mode. You then extract the .img file from the deathspl update.zip file, go into fastboot and flash the deathSPL using "fastboot flash hboot hboot.img". Flashing the deathspl direct using recovery CAN BRICK YOUR PHONE!
hi everybody!
some days ago i flashed my magic (TIM Italy, so 32A) whit the Magic_Rogers3.54.631.3 rom, that was a ruu exe file.
It flashed my spl and radio, that now are hboot-1.76.0010 (SAPP10000) and 6.35.16.19.
Now i wanted to change rom because of the language (i'm not able to put an italian dictionary when i write), but i don't succeed.. i tried to reflash the recovery, but i can't because fastboot says that is not possible to send data to the phone, so i can't also boot some recovery image.. same problem via adb or via terminal on the phone.
i rooted the phone with the last universal androot, but it's the same..
i succeeded to change recovery only with rom manager, but the phone doesn't go in recovery mode (it's still on the "rogers" splash screen), or if it goes, it reboot alone after a few seconds.
oh, at last, i'm not able to flash other rom, like the RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver or my original TIM rom.
I'll be really grateful to who will help me!!
thanks for reading!
download this application FlashRec
install it to your device
then download any of Amon_RA recovery imgs (HERE) (Choose the correct one for your device)
then push it to your sdcard
then open the FlashRec and press backup,
then write in the blank box "sdcard/xxxxx.img"
where xxxxx is the name of the img you pushed to your SD
then press flash .. if it is successful, connect your phone to adb
and write "adb shell reboot recovery"
I tried this on 32A 1.33.0010 and Radio 3.22,
I'm NOT 100% sure it will work with you,
try it at your own risk.
it says "phone type is EBI1/32A"
i press backup with or without the name in the box,and the result is
"backup failed: could not run command."
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
renedlog said:
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
Click to expand...
Click to collapse
I think you are right, because i was on stock 1.5 when i used this method.
OmarAta said:
I think you are right, because i was on stock 1.5 when i used this method.
Click to expand...
Click to collapse
me too... but the htc magic 32a with the actual stock rom, android 1.5 with sense form january, is already bugfixed.
Moving to General
sorry for the mistake, i thought it was the right section..
anyway i followed the guide in the post linked by renedlog and.. it worked!!! i didn't know where to put the flash_image file.. but it was written there.. so i did all, and now my rom is the RCMagic 5.0!
do you think it's good to try something different?
i use RCMagic 4.2
the version 5 is still a little buggy with the wake up from standby.
i will upgrade to an android 2.2 rom, if there is an update today for the 32B and hopefully it will be patched to my 32A.
yeah, i saw that bug.. it's really a pity, the rom was a little faster than the 4.2..
i suppose it would not be a big bug, so i hope somebody that is able will fix it!!
are there so big changes beetwen the 2.1 and 2.2?
After looking at few threads where members where asking for 1.29.401.16 RUU, and some of them finding an Image file of the same (including me) , but getting trouble to make it work like RUU. So i thought of writing a process to make it work if someone needs to get back to STOCK.
Requirements :
YOU NEED TO BE S-OFF
ALL DATA WOULD BE LOST,ALL MEANS ALL, SO BACKUP
DONT HOLD ME RESPONSIBLE IF ANYTHING GOES WRONG
PROCEDURE:
1. Download the 1.29.401.16 image file from here : https://docs.google.com/file/d/0B-4Hz5BkTjxdTV9fS01JbU5yTE0/preview?pli=1 of 1.29.401.16 ( Thanks to @west2cool for the RUU)
2. Download RUU_M7_UL_JB_50_Cingular.exe ( Link on http://forum.xda-developers.com/showthread.php?p=39588860 Thanks @BugsyLawson )
3. Execute RUU_M7_UL_JB_50_Cingular.exe
4. when all progress bars stop, go to %temp% search the most recent folder, and search for the file ARUWizard.exe file that inside of the folder {F46C5D93-D618-4028-943D-D8C5753929A3} (name may vary) and inside there is another {50F2F878-636A-496F-A7CB-544C067E0C4B} folder name will vary, inside this last one there is the file ARUWizard.exe
5. copy that last folder to some other place in your PC/Laptop
6. stop the executing of the RUU_M7_UL_JB_50_Cingular.exe
7. In the copied folder replace the "rom.zip" with the one in PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip, you need to rename PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip to "rom.zip", actualy this zip is a img file, that's why you can't unzip. ( Thanks to @torres.sis for this Guide )
8. Execute the ARUWizard.exe
Follow the onscreen instructions , and the device will be back to stock. You should not loose S-OFF, but the bootloader would be Relocked.
Just wanted to say thank you, it worked perfectly.
And I have been looking for the 1.29.401.16 RUU for a long time
Try this, more simple: http://forum.xda-developers.com/showthread.php?p=43693174#post43693174
i am currently on 2.24.401.1 firmware 4.2.2 ROM with hboot 1.54 S-OFF superCID . running this RUU will downgrade my hboot to 1.44 ??? also do i have to lock bootloader before running RUU?
cristian2206 said:
i am currently on 2.24.401.1 firmware 4.2.2 ROM with hboot 1.54 S-OFF superCID . running this RUU will downgrade my hboot to 1.44 ??? also do i have to lock bootloader before running RUU?
Click to expand...
Click to collapse
Yes, it will. No, you don't have to relock.
Sent from my HTC One using xda premium
cristian2206 said:
i am currently on 2.24.401.1 firmware 4.2.2 ROM with hboot 1.54 S-OFF superCID . running this RUU will downgrade my hboot to 1.44 ??? also do i have to lock bootloader before running RUU?
Click to expand...
Click to collapse
You could just flash the HBoot from this post instead if its just the hboot your after:
http://forum.xda-developers.com/showthread.php?t=2316726
@mathrania
I actually like your Idea as i had the very same idea just yesterday with the only difference that i was thinking it might be possible to adapt the meta inf from the ruu so we could actually create a full ruu that also flashes system this way. So we could make full RUU's from available components since Mike1986 chose to not share RUU's he gets.
Feel like diving into it?
Just a thought....
Sneakyghost said:
@mathrania
I actually like your Idea as i had the very same idea just yesterday with the only difference that i was thinking it might be possible to adapt the meta inf from the ruu so we could actually create a full ruu that also flashes system this way. So we could make full RUU's from available components since Mike1986 chose to not share RUU's he gets.
Feel like diving into it?
Just a thought....
Click to expand...
Click to collapse
How to do that?? I don't have much idea abt it...
Sent from my HTC One using xda premium
Does anyone have recovery image for 1.29.401.16 ?
hi bro i need a help,
htc 9088 not connecting with pc and no one near for repair, i lose password and during installation twrp crush real recovery mode. can u make a ruu file for my phone, firmware/recovery
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
Prerequisite
You should have installed:
K910 ADB Driver (available on the CD that appear when you connect the device)
ADB
Fastboot
Rooting
So the method is pretty easy:
Download the latest SuperSU update.zip and put it at the root of your Internal SD Card
(Optional) Download Google Apps for Android 4.2.2 (thanks to TeamAndroid) and put it at the root of your Internal SD Card
Download the recovery.img (build 140205)
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot cwm_recovery_custom.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
Update on the 6th of February (Build 140205):
Bigger font
/sdcard mounted on the first user's internal storage (= symlink /sdcard /data/media/0)
Makes use of the latest kernel
The old recovery.img stays available.
For those who would be stuck on K910_SS_S_2_040_0039_131101, I posted the official update.zip here
How to build my own recovery
If you are curious about building the recovery, I'll post here a few tips.
First of all, you'll need a good tutorial like the one on XDA University. The steps are the following:
Prepare your OS to receive a cyanogenmod repository. I would advice an Ubuntu so you can following this guide. Note that this is for a plain Android so you need to stop following it when they issue the first repo command
Then you need to carefully read this guide on porting CyanogenMod ROM. You don't need to build the full system (which is a completely other story) but only the recovery. I prepared the vendor directory for you (base on LG Optimus and a lot of research).
The building happens according to this guide.
You could be done by now if it wasn't for the dtb. If you try to boot your recovery as is, fastboot will complain about it. You'll find other people having the same issue, just follow their solution.
csu333 said:
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
So the method is pretty easy:
Download the recovery.img
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot recovery-clockwork-6.0.4.6-kiton.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
More precisions to come in a next edit.
Click to expand...
Click to collapse
Yess!!! Thanks!!!
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
QUOTE]
Same result for me too.
Click to expand...
Click to collapse
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
csu333 said:
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
Click to expand...
Click to collapse
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
sakilxda said:
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
Click to expand...
Click to collapse
I honestly doubt it: all the 1 click root I've seen until know are based on a bug in the backup mechanism that have been fixed for a while now. But since it seems pretty recent, anything is possible. I can't confirm since I'm rooted now
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
sakilxda said:
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Click to expand...
Click to collapse
You're right: best method is to upgrade then root with this method. If it seems difficult to get the upgrades, I can post the zip files (it took me more than a week to get the first one).
katalinscrob said:
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
Click to expand...
Click to collapse
You're very welcome
Well, actually, there should be no problem flashing this recovery, it's just that it could break the OTA process (and that I haven't tested it myself yet)
So next step after testing is to find a way to make this menu readable. I mean, I almost need a magnifying glass to read it :laugh:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
sakilxda said:
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
Click to expand...
Click to collapse
It is based on csu333's work. I linked thid thread to russian fellows.
katalinscrob said:
It is based on csu333's work. I linked thid thread to russian fellows.
Click to expand...
Click to collapse
Ok, just thought it was a copy
nlohani said:
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Click to expand...
Click to collapse
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
csu333 said:
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
Click to expand...
Click to collapse
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
katalinscrob said:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
Click to expand...
Click to collapse
Good suggestions. I'll take a look.
Now that I know what it takes to build a recovery, I'll think twice before starting a project of a really modded ROM
nlohani said:
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
Click to expand...
Click to collapse
I 've had the same behavior with the oldest ROM. This is why I provided a custom ROM with busybox installed even if I knew most people wouldn't need it. It was just impossible to install it afterwards. It might then be version related. Which version are you running?
Dummy friendly guide how to upgrade, flash and install the latest Marshmallow Firmware and the latest ROM’s such as the ViperOne ROM 4.x.x, this guide is intended for those who are already slightly familiar with the flashing process and have previously managed to flash a ROM on their HTC One M9 device…
CHECKLIST BEFORE STARTING:
1) Phone is S-OFF
2) Unlocked Bootloader
3) Rooted
4) Latest TWRP recovery
5) SUPER CID changed to 11111111
6) External SD Card
7) NANDROID Backup and any or every other form of backup
8) Device drivers, Android SDK Platform Tools including ADB & FASTBOOT.
9) USB Debugging enabled.
10) BACK UP OF ALL YOUR DATA !!!
Before we begin make sure you back up all your data on both the internal and external SD card.
For the purpose of this tutorial we will be installing the latest ViperOneM9 ROM…
a) Downloaded and place the latest ViperOne ROM - ViperOneM9_4.x.x.zip on your External SD card,
Main Thread by j to the 4n is found here:
http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Latest ViperOne ROM for download is here:
http://venomroms.com/htc-one-m9/
b) If you are currently on ViperOneM9 3.5.0 or older and wish to upgrade to the latest 4.x.x than the latest Marshmallow firmware is required (3.35.401.12 or 3.35.617.12 firmware)… This can be found here and within Sneakyghost original thread.
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Now download the latest version of either:
NO WIPE ZIP
or
FULL STOCK WIPE ZIP
For this tutorial we will use the FULL STOCK WIPE ZIP (to archive a clean install – this will wipe everything on your phone excluding the External SD card)
c) Place the downloaded M9_3.35.401.12_FullStock_wipe.zip into your Android SDK Platform Tools Folder (for example C:\Android\ if this is where all your tools are found)
d) Download the latest version of TWRP recovery from
http://www.teamw.in/devices/htconem9.html
Place the downloaded twrp-2.8.7.0-hima.img in your Android SDK Platform Tools Folder
e) Once you are 101% ready to begin the process start by connecting your device and launching the command window (hold shift, right click in window with all the required ADB/FASTBOOT aps and select "open command window here) once the black terminal window appears start by typing in
adb devices
if your phone appears in the list we can continue by typing:
adb reboot download
wait a few seconds for the screen to appear and type:
fastboot oem rebootRUU
your phone should now be in the RUU mode with a silver HTC logo, now type
(if you renamed the original file type its current name, by default it is as follows)
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
f) you will most likely receive something like this towards the end after running the above command...
FAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device...
just type the above command again and phone will flash the update again and hopefully it will take at least a minute or more to complete, hopefully there will be no more errors, just in case repeat the above command... Just in case you do see errors try looking them on Sneakyghost's thread found here
g) Once this is done and everything passed than we have successfully upgraded our firmware to Marshmallow... Since we selected the FULL STOCK WIPE option we need to flash TWRP once again (as it was wiped) and don't bother resetting or hoping for the phone to boot normally as it won’t...
(if you renamed the original file type its current name, by default it is as follows)
Type:
fastboot flash recovery twrp-2.8.7.0-hima.img
and once it’s done
adb reboot-bootloader
*if for any reason you need to reset your phone and gain access to the bootloader menu, download mode, recovery etc. you can always do this manually by holding vol up, vol down and power buttons at the same time for a few seconds to reset the device, to get into the bootloader, recovery, download mode etc. After the phone resets continue holding the vol down and power button until you reach the bootloader menu.
*if you type adb devices and you see multiple devices or emulators that prevent the commands from working I suggest running the following:
adb kill-server
adb devices
Now only your connected device should appear…
h) It is now time to enter our recently flashed recovery to finally install our latest ROM.
Enter the recovery manually or by typing
adb reboot recovery
From there you may select the wipe option (swipe to factory Reset) and proceed to the Install section, browse for your ROM file and select it.
i) Within Aroma installer select all your preferred options and begin to install, once the flashing completes your device should reboot and now you keep your fingers crossed and wait (will take several minutes so just be patient…. And DONE!!! You now have the latest Marshmallow firmware and ViperOneM9 ROM installed.
#Please note that I’m no expert when it comes to these matters, this guide is here to help anyone who is unsure what to do, I tried to write it up the best way possible (sorry that there are no fancy pictures) if there any errors or issues with my methods please feel free to correct them but so far they worked for me and hopefully will also work for you. (This guide will also help you flash other ROM's) If you need more help please feel free to ask, there is always someone here on xda who knows the answers
Excellent write up !!
Many thanks !!!....g
glad i could help
GODSPD said:
glad i could help
Click to expand...
Click to collapse
Very nice writeup. Just got an M9 for the wife. I've been around the block so I get everything, but I've been away from HTC since the One X...well, there's the N9 but it's a nexus. What are the RUU mode and Download mode. If I remember correctly there was only the bootloader to go to on the One X. If it's complicated is there somewhere I can read about the modes?
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
CrazyRom said:
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
Click to expand...
Click to collapse
PM sent, hope it helps.
zrzhu said:
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
GODSPD said:
PM sent, hope it helps.
Click to expand...
Click to collapse
Also try the following as error 22 was not covered in the error handling section...
http://forum.xda-developers.com/showpost.php?p=59783531&postcount=3
Download 7zip, open the zip inside of the program, right click on the Android text file and open within. Change the mid to yours hit save. It will ask if you want to update the zip, hit yes. Then try and flash.
SneakyGhosts post explains this:
Error 22 is new to me too but the string is kind of self explanatory: every archive has a header where the archive-program finds info about what type of archive and what compression. If the error says anything about this header, the logical conclusion is either a corrupted, broken archive or an unsupported archive type.
I suspect the latter simply due to the fact that the zip was unpacked and repacked, which then easily creates an incompatible zip.
GODSPD said:
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
Click to expand...
Click to collapse
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
zrzhu said:
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
GODSPD said:
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
Click to expand...
Click to collapse
Thanks. Hopefully ATT will release Marshmallow soon then.
Hi guys i dont have anymore pc. Can i flash new firmware without pc? Plz help
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
BLEK0TA said:
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
Click to expand...
Click to collapse
which exact files are you after, the android sdk?
thanks bro!! nice collection!
zrzhu said:
Thanks. Hopefully ATT will release Marshmallow soon then.
Click to expand...
Click to collapse
I'm still kind of "fuzzy" on this whole firmware thing.... IF I don't want to wait (on ATT) and IF I go S-OFF, which firmware can I/should I use for Marshmallow?
Delete
HI, can you please tel me how long does the firmware flash take as mine has been at it for over 2 hours? Not sure if it is stuck?
I am on sprint. How do i get the new firmware? It isnt on the list. Thank you