Related
Cheers Guys,
this guide will lead you to a S-Off HTC One Mini with SuperCID and Android 4.4.2.
NEW
Update to 4.4.2
NEW
Because my english sucks really hard, iam sorry in advanced for it
The S-Off guide is from the Handy-FAQ forum and just translated from german into english.
All thanks and greetings goes to them
http://www.handy-faq.de/forum/htc_one_mini_custom_roms/296446-htc_one_mini_s_off_supercid.html
Click to expand...
Click to collapse
The stock nandroid backup still uploading, pls bepantient.
You can do the s-off part of the guide if you wish.
People wich already got S-Off pls just skip that part.
Code:
[B][COLOR="Red"][CENTER]Neither phone FAQ , or assume I, nor the thread creator on XDA
responsibility for problems you encounter![/COLOR][/B][/CENTER]
Whats needed?
I tested HBoot versions 2.19 & 2.21!
Unlocked Bootloader over HTCdev
A rooted stock ROM & Kernel (Its important without it will not work!) JmzM4StockRootedOdex-WWE-1.22.401.1 & Jmz M4 Kernel
some knowledge how to use ADB and Fastboot
cmd-tool, every windows computer should have it
i could happen that it not work on the first time, just do it over again from beginning and it will work (i had that problem)
it does not looks very user-friendly (no GUI)
it will not brick your devices (BUT its possible because its a hack)
the possibility to get S-Off without problems is DAMN high
Download:
download Android SDK for ADB.
Download revone: http://revolutionary.io/revone
Guide:
You can use any OS for that guide, you just need an cmd-tool.
Download revone (above) and copy it to your adb folder, while Android is running.[/B]):
open cmd and use following commands:
Code:
adb push revone /data/local/tmp/
now use these commands:
Code:
adb shell
Code:
cd /data/local/tmp
Code:
chmod 755 revone
Prepare S-Off:
Code:
./revone -P
revone will give you an error now: "error message -2"
NOW Restart your device but leave USB debugging turned on and use following commands:
Code:
adb shell
Code:
cd /data/local/tmp
Code:
./revone -s 0 -u
revone should tell you that everything went fine and i got S-Off.
Here just some other commands for revone:
-u --> Unlock Bootloader
-l --> Lock Bootloader (It will not simply lock it, it will lock it like it was never unlocked)
-r --> Relock Bootloader (mark the device as unlocked)
-t --> "Tampered" will be removed from bootloader
!!!IMPORTANT! YOU NEED FULLY STOCK ROM, STOCK RECOVERY AND STOCK BOOT BEFORE YOU CAN USE THIS!!! fastboot oem writesecureflag 3 --> restore S-ON
If revone say OK then reboot your device into bootloader and check if you got S-Off[/code]
You should see S-Off Now.
Optional: Run revone (via CMD) and remove that tampered flag:
Code:
adb shell
Code:
cd /data/local/tmp
Code:
./revone -t
Credits
revone developed by Revolutionary dev team.
Disclaimer
Revolutionary dev team declines any responsibility if you use RevOne : If the world goes down, it 's not our fault . If your device ignites spontaneously , that's not our fault . Do you choose to use our tool, we do not force you.
Support
Please visit # revolutionary IRC on the Freenode network. We will support you as much as possible , but remember : This is an "early access" and we could just sleep or just not be available when you years of accession the chat. Just stay there and wait for a response.
Super CID :
Guide:
Boot into bootloader and connect via fastboot USB to your PC
open CMD to use (in my case) cd /Android/ (if your adb folder is on C:/Android/)
use following command
Code:
fastboot oem writecid 11111111
--> Its 8 times the 1!
now lets check it twice:
Code:
adb reboot bootloader
Or:
Code:
fastboot reboot-bootloader
Code:
fastboot oem readcid
--> You should see CID 11111111 now.
Now your device is S-Off!
Now lets install a custom recovery and a stock ROM to get the OTA.
Install TWRP Recovery:
Please visit this XDA Thread
http://forum.xda-developers.com/showthread.php?t=2418938
Click to expand...
Click to collapse
You can Download the latest touch recovery there.
rename it now to twrp.img and copy it to your ADB folder.
Guide:
Boot into bootloader and connect via fastboot USB to your PC
open CMD to use (in my case) cd /Android/ (if your adb folder is on C:/Android/)
use following command
Code:
fastboot flash recovery twrp.img
now use
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now enter recovery by selecting recovery from bootloader and enter it with power-button
Create now an backup (it shoudl take a lot of time cuz its almost stock device )
Reboot into android now
Now download this file:
https://mega.co.nz/#!dwgBXYwb!crFZggMODZoTDmVb-kfUIxczsWkitZDZQlqIxI1TnEA
Click to expand...
Click to collapse
My Link
https://mega.co.nz/#!ZtEmWZaT!dqCyvEDN1XrL5jh3sAMqvkBdW13yVNYejKEcrSqrlJ0
Click to expand...
Click to collapse
Thanks to scotty2000 for the mirror
You can google for an Stock 4.2.2 - 1.22.401.1 Odexed Nandroid Backup
Click to expand...
Click to collapse
Copy this nandroid backup into the TWRP backup folder.
Important (It should looks like /TWRP/BACKUP/SHA********** [Ur device ID]/Stock 4.2.2 - 1.22.401.1 Odexed/backup files)
Now reboot your device into recovery again and restore it with the backup we copied.
After it sucessfully restore your device boot it up
(Maybe TWRP will ask you to restore root, answer with NO!)
Wait until device booted and connect to WIFI.
Goto settings -> info -> Software-Updates and let him check for an OTA
If you have SuperCID you should get an OTA notification.
Download it but NOT install it.
Connect your phone to your PC and copy the OTA
(sdcard/downloads/) to your PC.
Reboot your device into Bootloader and open CMD
[Make sure you have WinRAR installed, its the only one wich worked for me]
Open the OTA file with winrar, inside it there is a firmware.zip file.
extract it somewhere or if you are lazy like me download it here
https://mega.co.nz/#!R4oEXRTR!BZgxVA4fi5QajU699fkF5QFARUdUCdS4Rl-Y3M_iVL8
Click to expand...
Click to collapse
Open the firmware.zip and extract the recovery.img and copy it to your adb folder.
Boot into bootloader and connect via fastboot USB to your PC
open CMD to use (in my case) cd /Android/ (if your adb folder is on C:/Android/)
now use
Code:
fastboot flash recovery recovery.img
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
now reboot your device into android.
Let it check for OTAs and if it show you that an OTAs was downloaded and waiting for install....
Install it!
Your device should reboot into Stock recovery and install the OTA.
It takes 5 - 10 mins after it the device reboots into a fresh & clean Android 4.3.
NEW 24.02.2014
After installed to 4.3 just look for a new Update.
You will get a notification that a new update is ready to download.
After downloading Android 4.4.2 just install it and... your done!
You can do now a factory reset to set the device up from beginning
If you want to root your device just download this file and install it via recovery:
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Click to expand...
Click to collapse
Thanks tbwshaun for the Link
For kitkat (4.4.2) User, pls use this SuperSU.zip to get root.
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.93.zip
Click to expand...
Click to collapse
But if you to lazy to go to recovery to flash stuff just use Flashify App
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=de
flash it from running android and simply reboot
(You can flash boot.img & recovery.img also with this app)
And i can also confirm that Xposed Framework & Sense Toolbox
http://repo.xposed.info/module/de.robv.android.xposed.installer
Click to expand...
Click to collapse
wich is used in ARHD Roms, works very well too.
It has a lot of custom stuff in it
I already did it to 6 devices now and it works without problems.
The devices was from Vodafone, O2, Telekom and many others
have you uploaded the stock rom yet mate?
tbwshaun said:
have you uploaded the stock rom yet mate?
Click to expand...
Click to collapse
He's uploading. You can see the status on the original post, in a grey case "uploading"
Thanks a lot for this. One question though: I have already got S-OFF with rumrunner. Can I get S-OFF "again" with ReVone, so I can later return to S-ON if I need to return my phone for warranty repair?
Sent from my HTC One mini using Tapatalk
all i need now is this nandroid back up and i can carry on???????????????????
@MirageBlader,
1. I'm now on stock rom (not jmz's) and rooted. Can I s-off mine?
2. What happened if I just let s-off without flashing other rom? will mine be just fine? because I read in another thread, @jmz said I will encounter boot loop
thx
edimonoarfa said:
@MirageBlader,
1. I'm now on stock rom (not jmz's) and rooted. Can I s-off mine?
2. What happened if I just let s-off without flashing other rom? will mine be just fine? because I read in another thread, @jmz said I will encounter boot loop
thx
Click to expand...
Click to collapse
You just have to relock bootloader with fastboot and boot looping is gone
Sent from my HTC One mini using Tapatalk
Aciz said:
You just have to relock bootloader with fastboot and boot looping is gone
Click to expand...
Click to collapse
Ok, I'll try. Thx for the reply
---------- Post added at 05:02 PM ---------- Previous post was at 04:25 PM ----------
Aciz said:
You just have to relock bootloader with fastboot and boot looping is gone
Click to expand...
Click to collapse
One more thing @Aciz, should i relock the bootloader with ..
Code:
./revone -l
Or..
Code:
./revone -r
?
Thx
edimonoarfa said:
Ok, I'll try. Thx for the reply
---------- Post added at 05:02 PM ---------- Previous post was at 04:25 PM ----------
One more thing @Aciz, should i relock the bootloader with ..
Code:
./revone -l
Or..
Code:
./revone -r
?
Thx
Click to expand...
Click to collapse
I haven't used this method yet, since I used rumrunner to get my S-OFF. But I locked it with fastboot with
Code:
fastboot oem lock
Sent from my HTC One mini using Tapatalk
Its still uploading. And Iam still at work. To do s-off u need the rooted Rom and custom kernel, I tried it without and it's not working but if u have fully stock make a system dump to be safe. If u have s-off it doesn't matter if the boot loader is unlocked or locked. U just need it later if you have to sent it back to HTC. I will keep you guys updated with the upload. I will also upload a system dump of my currect 4.3 system. But u all need s-off.
Gesendet von meinem HTC One mini mit Tapatalk 4
Here you go:
https://www.dropbox.com/s/jjuxseb8s0pceuw/Stock 4.2.2 - 1.22.401.1 Odexed.zip
Pls don't just use it, pls upload it somewhere else to and share the link. Tapatalk don't let me edit my thread so I will add it later
Gesendet von meinem HTC One mini mit Tapatalk 4
@MirageBlader Can remrunner be used in the new update or is revone the only option?
I dunno, maybe yes. I used this methode and I can confirm that it work so. Try rumrunner and tell us if it's working
Gesendet von meinem HTC One mini mit Tapatalk 4
Cheers ^^ I'll report my experience with rumrunner S-OFF at weekend if no one has done it prior to that.
Sent from my HTC One mini using Tapatalk
hello all im just downloading the update now 2.12.401.1 i will post when i have successfully done it!!!!!
---------- Post added at 09:10 PM ---------- Previous post was at 08:32 PM ----------
I can comfirm that this guide works im now running android 4.3 with sense 5.5 love it!!!!!!!
im uploading the nandroid back up again so i will post link once uploaded!!!!!
thanks to @MirageBlader
If you require any help please dont hesitate to ask!
I'm confused, do I need the JmzM4StockRootedOdex-WWE-1.22.401.1.zip installed before doing the Nandroid backup currently on Magio R4, but my battery started to sweat and now I want to put it back to stock HTC 4.2.2 so I can get warrenty repair. I have done everything right up to flashing TWRP.
tbwshaun said:
hello all im just downloading the update now 2.12.401.1 i will post when i have successfully done it!!!!!
---------- Post added at 09:10 PM ---------- Previous post was at 08:32 PM ----------
I can comfirm that this guide works im now running android 4.3 with sense 5.5 love it!!!!!!!
im uploading the nandroid back up again so i will post link once uploaded!!!!!
thanks to @MirageBlader
If you require any help please dont hesitate to ask!
Click to expand...
Click to collapse
did you do the revone s-off method?
reubendevries said:
I'm confused, do I need the JmzM4StockRootedOdex-WWE-1.22.401.1.zip installed before doing the Nandroid backup currently on Magio R4, but my battery started to sweat and now I want to put it back to stock HTC 4.2.2 so I can get warrenty repair. I have done everything right up to flashing TWRP.
Click to expand...
Click to collapse
You need this Rom and kernel to do s-off, after it you need the nandroid backup to get the 4.3 ota
Glad that u got it
Gesendet von meinem HTC One mini mit Tapatalk 4
I take it they well be a system.img made for a dump
Sent from my HTC One mini using Tapatalk
hani1 said:
did you do the revone s-off method?
Click to expand...
Click to collapse
was this for me? If so Yes I did and was able to get the tampered message away, what I would like to do ideal is load 4.2.2 stock back on it and then relock the bootloader so that I can return it to HTC without them lifting an eyebrow. The battery started to swell, and pushing out the back and now the screen is starting to bleed red. So I want to put it back to stock and return it, I don't want them to void the warranty because of software due to a major hardware malfunction. If you want to see photos check out my thread here
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
MirageBlader said:
You need this Rom and kernel to do s-off, after it you need the nandroid backup to get the 4.3 ota
Glad that u got it
Gesendet von meinem HTC One mini mit Tapatalk 4
Click to expand...
Click to collapse
I was able to do the S-OFF with the Magio R4 rom though... should I still switch over to the other Rom? Maybe make sure that installing Specific ROM and Kernal is step one if that is the case.
Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo
ipk1 said:
Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo
Click to expand...
Click to collapse
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.
Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
You don't need to do anything with your hboot, it's fine
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
sudo adb flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
And ... I hope this is not the wrong forum. If so, really sorry ...
Click to expand...
Click to collapse
It is - questions should be posted in the Questions subforum :silly:
SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.
Click to expand...
Click to collapse
all right. thanks. i found that recovery and did
sudo fastboot flash recovery 4EXT_Recovery_Touch_v1.0.0.6_RC1.img
when i go into recovery then, again nothing ... phone is stuck in the white screen. sorry. with white screen i meant the splash screen, which is white on my phone, but has the telecom logo. so i think the screen is allright.
so i pulled the battery and back to cwm (flashed the cms recovery and voila).
Aquous said:
Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
Click to expand...
Click to collapse
absolutely. that's why i came here. the phone was fine under htc sense, so its not the phone. it got to be me.
Aquous said:
You don't need to do anything with your hboot, it's fine
Click to expand...
Click to collapse
Good.
Aquous said:
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
oh. typo. sorry.
Aquous said:
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This boots into recovery. But not exactly. It boots to the white Telekom screen, and then it reboots and goes into recovery. Since I found that strange I extracted the boot image once more from the flinny...zip and tried again. confirmed.
Aquous said:
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Click to expand...
Click to collapse
Downloading. This is "SVHD v2.1.0 by mygamers (MultiDevice)", right ? The thing is huge. That's gonna take a bit and I have to go to work. Get back to you later ...
Aquous said:
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
It is - questions should be posted in the Questions subforum :silly:
Click to expand...
Click to collapse
I extracted the boot.img
Can somebody move this ?
SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
GL.
Click to expand...
Click to collapse
4ext touch 1.0.0.6 RC1, same problem. stuck at the white telekom screen.
twrp-2.7.0.0-saga-recovery.img, same problem.
but openrecovery-twrp-2.6.3.0-saga.img did work
Ingo
Aquous said:
I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good.
Click to expand...
Click to collapse
tdDDAAA !!!
So I installed the SVHD .zip with TWRP 2.6 (see above) and that did go nowhere yet.
But I then extracted the saga boot image from that zip kernel/saga/boot.img, renamed that to avoid confusions, and then
<code>
fastboot boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
And my Telekom splash screen blinks up, then the HTC sense (quietly brilliant), and some 3 minutes later ... it worked.
Flashing
<code>
fastboot flash boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
MY guess is it was the reformatting to ext4 ... is that something I should have done all along ? Or any other idea ?
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Yeah,check panel now.Some phones has that problem.If you have hitachi then I'm sorry.From what I know no1 make MDDI kernel anymore.
teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Must be, since I tried to install blindnnumbs cm now, and same problem, again ... Good ... so back to SVHD and check that thread. Thanks.
Ingo
One more thing:
On the link you provided the instructions are given as follows, and i am not 100% clear on everything:
1) Wipe all data
2) Flash your custom ROM
3) Get your MDDI compatible kernel and flash it
--> IF (and only IF) you've this error when flashing kernel in recovery: assert failed:write_raw_image("/tmp/boot.img","boot"):
--> 3a) extract boot.img from custom rom ZIP and put it in the adb directory on your PC
--> 3b) reboot in fastboot mode
--> 3c) execute from PC: fastboot flash boot.img
--> 3d) reboot in recovery and retry to flash your new kernel
--> 3e) Now, flashing kernel is completed and you can continue to Step 4)
4) Get new boot.img: in recovery, attach USB cable and run from PC terminal --> adb pull /tmp/newboot.img (it will trasfer generated boot.img to your PC) <--
5) On your PC rename newboot.img file to boot.img
6) Reboot in fastboot mode
7) Install new boot.img (from PC terminal execute --> fastboot flash boot.img <--)
So I
- in twrp i installed cm-10.1-20130709-UNOFFICIAL-saga.zip (blindnnumb cm-10.1, penultimate version. the very last version does not unzip, no matter how many times i download it)
- then flashed fastboot flash boot cm-10.1-20130709-UNOFFICIAL-saga.img
- then flashed fastboot flash boot saga_mddi_291212.img (from your link)
- i pulled newboot.img and then flashed newboot.img
and i am stuck again ... but maybe i did not totally understand the instruction from above ? i.e. 2). do i need to install the zip and the img ?
also in line 7) the command seems to be wrong. right ?
ingo
If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img
teadrinker said:
If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img
Click to expand...
Click to collapse
Oh my ... that did not go either. Now I flashed
cm-10-20121116-EXPERIMENTAL-saga-NK111.zip
saga_kernel_82n_4.0_4.1.zip (which does not seem to produce a newboot.img, and does not have a boot.img either)
that, at least, brings up the spinning clockworkmod wheel ... but then that's that, too ...
oh well ... i guess SENSE it is gonna be then ...
ingo
Didn't you read the warning at the top of the hitachi panel thread? It said:
WARNING!
ALL THE LATEST 4.1.x AND 4.2.x ROMS DO NOT SUPPORT HITACHI SCREEN PANELS, EVEN AFTER APPLYING THE CORRECT MDDI KERNEL!
THIS APPLIES TO ROMS THAT ARE BASED ON AOSP, AOKP, CyanogenMod, ParanoidAndroid, PAC-Man, etc., AND ROMS THAT ARE BASED ON MIUI
THE LAST CUSTOM ROM THAT DOES SUPPORT MDDI PANELS IS CyanogenMod 10.1 Build 13 by Flinny, SO THE DATE WHEN BUILD 13 WAS RELEASED IS YOUR GUIDE TO CHOOSE THE CORRECT ROM THAT WILL BOOT UP AFTER FLASHING THE MDDI KERNEL
Click to expand...
Click to collapse
Aquous said:
Didn't you read the warning at the top of the hitachi panel thread? It said:
Click to expand...
Click to collapse
Read it ... and I think I did not understand it right ... I guess I got too tired over it. I thought I had one that should match those criteria. Tomorrow is another day ...
Ingo
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
RBraverman said:
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
Click to expand...
Click to collapse
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
cmendonc2 said:
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
Click to expand...
Click to collapse
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
RBraverman said:
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
Click to expand...
Click to collapse
Hope you get getter
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
cmendonc2 said:
Hope you get getter
Click to expand...
Click to collapse
Thank you, slowly on the mend.
cmendonc2 said:
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
Click to expand...
Click to collapse
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
So I need 3 things: newest F/W (have), Latest TWRP(don't have - yet but looking, 2.7 I believe), latest way to root(don't know) - Correct?
Again where is that thanks button!!!!!
RBraverman said:
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
Again where is that thanks button!!!!!
Click to expand...
Click to collapse
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
cmendonc2 said:
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
Click to expand...
Click to collapse
NOW it's there!
Okay upping to stock F/W, looking for TWRP (openrecovery-twrp-2.6.3.0-tf300tg-JB.img) then how do I root this
RBraverman said:
NOW it's there!
Okay upping to stock F/W, looking for TWRP - how do I root this
Click to expand...
Click to collapse
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
cmendonc2 said:
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
Click to expand...
Click to collapse
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
RBraverman said:
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much mroe optimized for older devices, and you should see a performance upgrade.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Click to expand...
Click to collapse
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much more optimized for older devices, and you should see a performance upgrade.
Click to expand...
Click to collapse
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
RBraverman said:
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
Click to expand...
Click to collapse
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
cmendonc2 said:
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
Click to expand...
Click to collapse
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Just rebooted, and it's 4.2.1, but everything I had - most of what I had, is still there!?! And the run?
RBraverman said:
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Click to expand...
Click to collapse
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
cmendonc2 said:
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
Click to expand...
Click to collapse
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
RBraverman said:
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
Click to expand...
Click to collapse
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
cmendonc2 said:
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
Click to expand...
Click to collapse
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
RBraverman said:
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
Click to expand...
Click to collapse
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
cmendonc2 said:
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
Click to expand...
Click to collapse
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
RBraverman said:
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
Click to expand...
Click to collapse
I'm not sure what you are talking about with "fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img". As long as TWRP is working you shouldn't have to use fastboot anymore.
The new bootloader that you upgraded to only has 3 icons when you press vol-down and power. Fastboot now connects automatically if you turn on your tablet with the USB plugged in and pressing the key combo. To access TWRP, selecting RCK is the correct choice. As always, never select the Wipe Data in the bootloader menu or you will brick.
Before flashing new ROMs, you should only have to do the "swipe to factory reset" option in the TWRP recovery. If you update your ROM with a newer version of that specific ROM, you only have to Wipe Cache and Dalvik Cache.
complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) then power off your device
4) go to fastboot mode
( by pressing vol- + power buttons simultaneously)
5) then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :
#reserved
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Thank you very much!!!! Was looking for this in a pretty long time!!!
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.
camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?