Develop Bugs

Sorry, just a mess

But thank all you guys to point it out

Very kind, hope it helps many.

Should we format /system qheb installing rom? When is the best time to wipe battery stat?
Sent from my GT-I8150 using Tapatalk

FelixAusChina said:
[HOW TO]root, flash custom recovery ClockworkMod v5.5.0.4 and ROM Customized 1.8Ghz ROM (now with experiment EUR OC ROM) without odin step by step from offical ROM 2.3.6
1. Root your phone
Rooting via Recovery mode(SD card)
a. Download this Zip-file http://dl.dropbox.com/u/47601401/update.zip copy this into the internal SD card.
b. While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on. At last press the menu button quickly while pressing the other two buttons.
Note: This instructions is written for the stock recovery. Custom recoverys should work very similiar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
c. Navigate with the volume up and down to apply sdcard:update.zip in Recovery Menu. Use the home-button to confirm your selection.
d. Choose (with volume buttons) the update.zip file on your internal sd card and confirm again with Home-button. You will have to wait for several seconds.
e. Now choose reboot system now and confirm with home button.
Now you device should be rooted.
The link: http://forum.xda-developers.com/showthread.php?t=1317394
2. Enable recovery ClockworkMod v5.5.0.4 with flashing in adb shell.
Don't flash the zip file, but extract and flash the img file
a. Root your devece(look above)
b. Copy downloaded recovery ClockworkMod v5.5.0.4http://www.multiupload.com/KTNBHX6JBG on internal sdcard
c. Disconect phone from copmuter and make sure that USB debugging is on
d. Connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer)
e. Download the adb shellhttps://rapidshare.com/files/1061144422/android-sdk-windows.zip
note:If you just want to obtain and perform adb command, rather than to develop Android software, in fact, there are many adb streamline packets in internet, don't need the full Android SDK.
As the android-sdk version started from r08, adb wasn't contained in the downloaded files from the beginning, but was downloaeded by SDK Manager after that, and adb wasn't under the original tools directory. To maintain the text of the description of teaching would continue to apply the screen, I made ​​out of adb streamlined package from the r07 version.
f. Extract the file android-sdk-windows.zip into the root directory of C for teaching easily
g. open command prompt
windows 7: start-all programs-accessories-command prompt or search cmd
h. Then in the "Command Prompt" window, type the following command to switch to the adb directory
c:
cd c:\android-sdk-windows\tools
i. Enter the "adb shell", enter the phone to start the next command (think of it as the phone has a similar "command prompt" environment)
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
j. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded.
3. Download which ROM you like
4. Put the zip into Internal SD
5. Boot into ClockWorkMod, backup your current ROM using nandroid (just in case) then, use Install menu to Wipe data/cache and to install it from the SD card.
By the way, when you enter into the ClockWorkMod recovery, press the volume up-down-up for 3 times, you will see the option "go back" in the recovery menu.
Click to expand...
Click to collapse
By this method, is our bootloader is still locked?

Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
Click to expand...
Click to collapse
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!

i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/showthread.php?t=1376196 i just followed that way...

irishpancake said:
Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!
Click to expand...
Click to collapse
i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/show....php?t=1376196 i just followed that way...

OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
adb shell
$su
#dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
This is what ppl will have to write into the dd command
if = input file.....of = output file
Use dd cautiously, improperly entering the wrong values could inadvertently wipe, destroy, or overwrite the data on the hard disk drive or device memory
Click to expand...
Click to collapse
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......

irishpancake said:
OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
This is what ppl will have to write into the dd command
if = input file.....of = output file
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......
Click to expand...
Click to collapse
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW

Felix, I give up....but thanks for taking on board my suggestion....it may just save someone from a major catastrophe.
thanx again
ATB

FelixAusChina said:
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW
Click to expand...
Click to collapse
The point is - why include the first (i.e. incorrect) version of the command at all? It would be much clearer just to include the correct version, after the change you mention. Including the incorrect version just makes the instructions more confusing.

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Man, don't cry!!!!
sorry for being so blunt, but it's important, especially when using adb, and commands like dd to get it exactly right/correct......
we don't wanna brick anyone's phone
But, thanks anyway, the guide is basically good!!!
cheers, OK

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Don't mistake directness for hostility.
We didn't want you to remove your guide completely - we're just trying to help improve the quality of it, for everyone's sake. Collaboration is what this forum is all about.
Restore the guide, make the suggested improvements, and let's see if we can make it even better.

[TUT] [ROOT] Backup restore IMEI manually

Automatic Backup Restore IMEI TOOL by Sector1369 is HERE .
(Only Require Custom recovery)
Automatic backup restore CMD script added by "deadlyindian" at Post#5
(Require PC ,ADB drivers & Root permissions )
If you still want to do this manually, look below
IMEI backup of redmi 1s
Require ROOT permissions
We all known that EFS partition holds the imei,sn ,wifi mac & other important data.
In Snapdragon the EFS partition are modemst1 ,modemst2 & FSG partitions. so it's important to take backup of these partitions.
1.connect your phone to PC , adb debugging enabled & goto adb shell by,
Code:
adb shell su
OR
Open terminal emulator app in your phone & take super user permissions, by
Code:
su
2.type following commands to backup imei partitions.
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16_modemst1
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17_modemst2
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20_fsg
also these are some important partition you should consider to backup.
modem, fsc, bk1, ddr.
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
Now the backup is stored in you internal storage ,store these files in safe place.
in case u get invalid imei or unknown, restore these partitions.
To restore these partitions,
Code:
dd if=/sdcard/mmcblk0p16_modemst1 of=/dev/block/mmcblk0p16
dd if=/sdcard/mmcblk0p17_modemst2 of=/dev/block/mmcblk0p17
dd if=/sdcard/mmcblk0p20_fsg of=/dev/block/mmcblk0p20
dd if=/sdcard/mmcblk0p23_modem of=/dev/block/mmcblk0p23
dd if=/sdcard/mmcblk0p9_DDR of=/dev/block/mmcblk0p9
dd if=/sdcard/mmcblk0p12_bk1 of=/dev/block/mmcblk0p12
dd if=/sdcard/mmcblk0p18_fsc of=/dev/block/mmcblk0p18
Working on Aroma EFS backup restore tool..
NOTE:-
Don't use tools or commands from other device because different devices has different partition address, that will result in wrong backups.
To use this method to backup other phones EFS , u should find your partition info.
Redmi 1s Partition tables can be found HERE
ENJOY,

Thanks man...it would be alot helpful if i gone to any trouble [emoji7]

But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.

pgreed said:
But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.
Click to expand...
Click to collapse
i know but it's always better to take bakup,who knows what 'll happen...
there is no way to generate imei,wifi mac data for qualcomm (as far as i know) ...
so it will come handy...

Auto IMEI Backup & Restore Tool
Backup restore IMEI Automatically
FIRST INSTALL THE ADB DRIVERS FOR THE 1S ► GO HERE ◄
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
NOTE : Enable root access for adb if you're on Custom ROM based on CyanogenMod
to do that ► Open Settings ► Superuser ► Superuser Access ► Select Apps and ADB ► done
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S

deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
It working perfectly.Thank you.

pgreed said:
It working perfectly.Thank you.
Click to expand...
Click to collapse
You're Welcome :good:

[Backup restore IMEI Automatically] works like charm. thanks :good:

lavizta said:
[Backup restore IMEI Automatically] works like charm. thanks :good:
Click to expand...
Click to collapse
im glad it help :good:

deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
Great work :good::good:

None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Sector1369 said:
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
ENJOY,
Click to expand...
Click to collapse

kapil.git said:
None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Click to expand...
Click to collapse
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.

rkkaranrk said:
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.
Click to expand...
Click to collapse
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.

kapil.git said:
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.
Click to expand...
Click to collapse
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:

it might come in handy or it might not
nevertheless i'm putting it in safekeeping.
thanks for the work & effort.
:good:

rkkaranrk said:
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
Click to expand...
Click to collapse
Yes you are correct , been using Sony for a while
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:
Click to expand...
Click to collapse
mmmkaay..

@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 （V5） " in case if you need.

ADB Drivers & instructions...
fanboy_android said:
@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 （V5） " in case if you need.
Click to expand...
Click to collapse
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

deadlyindian said:
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
Click to expand...
Click to collapse
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.

fanboy_android said:
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.
Click to expand...
Click to collapse
Done!!

New Update Asia (1.62.707.4....) (And a lil help??)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got this update few hours ago....
though not able to flash it(After flashing stock recovery ie.)
any1 mind telling me how i can update?
Thnx in advance

system has been remounted r/w reflash device to re enable ota updates
this is the error i get
http://fotadl.htc.com/secure/OTA_HI...1.61.707.4_release_443364hpmfqulmgf0g5meu.zip
this is the url i got when i took a logcat during downloading the update... though i cant access it
and looking here: http://forum.xda-developers.com/showthread.php?t=1606676
if u take a look at ota urls it is similar eg- http://fotadl.htc.com/OTA_ENDEAVOR_....14.401.27_release_302022scz3ve3d2k8wy15p.zip
but the difference is i cant access the above url but this one works just fine
just curious. I'd really appreciate if some1 could answer

T3snake said:
system has been remounted r/w reflash device to re enable ota updates
this is the error i get
http://fotadl.htc.com/secure/OTA_HI...1.61.707.4_release_443364hpmfqulmgf0g5meu.zip
this is the url i got when i took a logcat during downloading the update... though i cant access it
and looking here: http://forum.xda-developers.com/showthread.php?t=1606676
if u take a look at ota urls it is similar eg- http://fotadl.htc.com/OTA_ENDEAVOR_....14.401.27_release_302022scz3ve3d2k8wy15p.zip
but the difference is i cant access the above url but this one works just fine
just curious. I'd really appreciate if some1 could answer
Click to expand...
Click to collapse
wow, that's some annoying thing. I'm not sure what goes on with this, seems like detects if the system partition was tampered with at some point?!
I guess it was with a restored backup of system partition without any modifications, but probably just the restoration process from a backup results in differences to an original System data partition. I have checked the Taiwan OTA zip (unfortunately I can't build a rom from that), and it contains a system diff block patch, which my guess is that takes unmodified system quite seriously, but I'm not familiar how HTC does this part these last years. I was always using custom ROMs when I unlocked my phone, so I have to admit, I'm not sure when HTC ota process is being blocked by the update binary..
All I can help with is to promise i'll update the CleanSlate when I get my hands on a system image with the new base and get some free time to mess with it...

tbalden said:
wow, that's some annoying thing. I'm not sure what goes on with this, seems like detects if the system partition was tampered with at some point?!
I guess it was with a restored backup of system partition without any modifications, but probably just the restoration process from a backup results in differences to an original System data partition. I have checked the Taiwan OTA zip (unfortunately I can't build a rom from that), and it contains a system diff block patch, which my guess is that takes unmodified system quite seriously, but I'm not familiar how HTC does this part these last years. I was always using custom ROMs when I unlocked my phone, so I have to admit, I'm not sure when HTC ota process is being blocked by the update binary..
All I can help with is to promise i'll update the CleanSlate when I get my hands on a system image with the new base and get some free time to mess with it...
Click to expand...
Click to collapse
Here is update-script on OTA.
Code:
# ---- start making changes here ----
([COLOR="Red"]range_sha1("system", "2,0,1") == "c3b8ad46808545e81168538a78b9af707acedceb") || (range_sha1("system", "2,0,1") == "b69f6ab8e68d0df61090527a1575eb052456f3b3") || abort("system has been remounted R/W; reflash device to reenable OTA updates");[/COLOR]
if range_sha1("system", "..." then
ui_print("Patching system image...");
show_progress(0.900000, 0);
block_image_update("system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
else
(range_sha1("system", ...
abort("system partition has unexpected contents");
endif;
It means it will check the SHA1 code for system partition before applying OTA.
If you initial issue the twrp in here,it will mount system as rw and destroy the SHA1.
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 [B][COLOR="Red"] rw [/COLOR][/B] wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,autoformat
Maybe someone could repack the m9+ recovery here with the new version twrp2.8.7.0,the issue should be resolved.

yvtc75 said:
Here is update-script on OTA.
It means it will check the SHA1 code for system partition before applying OTA.
If you initial issue the twrp in here,it will mount system as rw and destroy the SHA1.
Maybe someone could repack the m9+ recovery here with the new version twrp2.8.7.0,the issue should be resolved.
Click to expand...
Click to collapse
What if we remove that part of the code in updater script...
Btw did u get hands on the ota file its tiring to download it after every unsuccesful flash

T3snake said:
What if we remove that part of the code in updater script...
Btw did u get hands on the ota file its tiring to download it after every unsuccesful flash
Click to expand...
Click to collapse
No,you will reach the "system partition has unexpected contents"
Code:
else
(range_sha1("system", ...
abort("[COLOR="Red"]system partition has unexpected contents[/COLOR]")
The OTA file was laid on /data/data/com.htc.updater/files ,if you have rooted, copy it out to your SDCard.

yvtc75 said:
No,you will reach the "system partition has unexpected contents"
Code:
else
(range_sha1("system", ...
abort("[COLOR="Red"]system partition has unexpected contents[/COLOR]")
The OTA file was laid on /data/data/com.htc.updater/files ,if you have rooted, copy it out to your SDCard.
Click to expand...
Click to collapse
what if i replace abort command with print command?
Will there be an syntax error?
or i remove the part u mentioned too?
btw i unrooted thru supersu app yesterday.... still not updating
ill try to get ota file thru adb pull
EDIT: Adb pull gave 0files pulled 0 files skipped
EDIT2: I took a logcat while updating my device
W/htcCheckinService_CheckinRecoverySystem( 850): !!! REBOOTING TO INSTALL /data/data/com.htc.updater/files/OTA_HIAU_ML_TUHL_L50_SENSE70_MR_hTC_Asia_WWE_1.62.707.4-1.61.707.4_release_443364hpmfqulmgf0g5meu.zip
Click to expand...
Click to collapse
if it helps any1
now ill be rooting my phone again
thnx all for help

i removed all the abort commands and it broke my rom
cant mount system
(Flashed thru twrp)
Very bad idea

Q beta 5 is GREAT,but can not mount /system for now

I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)

seardna said:
I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)
Click to expand...
Click to collapse
Happened to me before. I believe I cleared the system partition and it worked.

TechNash said:
Happened to me before. I believe I cleared the system partition and it worked.
Click to expand...
Click to collapse
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .

seardna said:
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .
Click to expand...
Click to collapse
Latest TWRP from website, magisk stable

TechNash said:
Latest TWRP from website, magisk stable
Click to expand...
Click to collapse
Thanks. But can you mount system in the TWRP? While install Magisk , there are some errors failed to mount /system (Invalid argument )

Would this be why titanium backup doesn't open either ??

this happened with beta 4 also. don't know if it's twrp or magisk issue

Q5,same issue here, tried everything, factory reset, format partition, no luck
apart from this, everything works
in root explorer, you can't mount R/W

A latest magisk alpha version maybe solved this problem .
Here is the custom channel :backup up FIRST!
https://raw.githubusercontent.com/yzkpqv68745/magisk/master/alpha.json

solución
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.

ismael47 said:
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.
Click to expand...
Click to collapse
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
darkoj2007 said:
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this
Click to expand...
Click to collapse
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.

I'm on official release 10.0.0 (QP1A.190711.020, Sep 2019) flashed without "-w" over android 9. Pixel 2.
Flashed latest TWRP (3.3.0-0) and 19.3 Magisk, then latest canary. Nothing helps.
Did you manage to find solution? I would appreciate any help.

ismael47 said:
[/IMG]
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.
Click to expand...
Click to collapse
Dude that does seem to work at least for the magisk install. It doesnt help fix other issues like adaway and titanium backup from not being able to mount system though!
Appreciate your effort anyway

There's a setting in magisk that'll allow you to install adaway. Systemless hosts...tap it then reboot and adaway should install.
That worked for me.

I was able to get /system to mount by going to Advanced Wipe and selecting 'system' and choosing repair -> Change File System - EXT2 then go back and switch it back to EXT4.
I have not been able to get /vendor mounted and I believe it is because the syntax used has changed.
I read that AOS10 uses a form of EXT4 that preserves it as ready only, possibly by filling the used space of the drive preventing any writing.
This explains some of the new obstacles TWRP must compensate for in order to maintain compatibility w/ AOS10
https://source.android.com/devices/architecture/kernel/mounting-partitions-early
I have had luck installing Magisk by enabling USB Debug and typing in ADB shell:
cat /dev/block/sda19 > /sdcard/boot.img
Open Magisk and chose to install to file and select the boot.img.
Replace boot.img in the zip file that contains Android 10 factory firmware.
Current Marlin factory firmware [ https://dl.google.com/dl/android/aosp/marlin-qp1a.191005.007.a1-factory-c27241e0.zip ]
Inside marlin-qp1a.191005.007.a1-factory-c27241e0.zip is another archive: image-marlin-qp1a.191005.007.a1.zip ; inside this archive is boot.img.
Using 7zip you can open this archive and drag / drop boot.img replacing the stock image with the Magisk patched one.
Run Flash-all.bat, note it *WILL Wipe* your device but include a Magisk patched boot.img.
Once you finish initial setup of phone, download magisk manager and when you open it, it will automatically patch and reboot your phone enabling root. (make sure you have internet connection before opening magisk manager)
After you have root enabled phone you can customize /system to your liking and then cat /dev/block/sda33 > /sdcard/system.img to replace the firmware version.
(Still am not able to load /system as RW using FX, so have yet to be able to modify .props)
You can locate the various links and identify if you are using slot a/b by typing in TWRP terminal : ls -la /dev/block/by-name/
Side note:
The wizard himself has delicate and important matters of being a present father and managing the obstacles of keeping the brood happy-content and also providing nurturing support to the new addition and persistent validation for the wifey. [Congrats])
(apologies for improper formatting de-pretyfied by inotoxication)

How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!

*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana

Wow you know how long I have been waiting for this?
I did not test it yet but I will soon, hopefully today. Will work with both Dev image and regular image?
Thanks @mrhamed
By the way, Do you know if this method also works on a 2017 Pro 16gb version?

This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mrhamed said:
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
Click to expand...
Click to collapse
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?

cHECKjAM said:
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
Click to expand...
Click to collapse
It's my device screen.
I don't like to lock-bootloader, so AI not works at this time, I'm testing "MagiskHide Props Config" to try hide the booloader-state and I hope enable AI with unlocked bootloader:
https://forum.xda-developers.com/showpost.php?p=83972471&postcount=4626

@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
What Im hoping is that bluetooth will work. Because when I flash the dev image earlier and used the ↑ ↑ ← ← method and choose skip setup, bluetooth has not been working. Can not find any bluetooth devices when i search for them. The same problem on 2 different devices.
So now Im trying this method right now to see if it works better.
If it does not work I need to try the the none-developer image instead.
However this method seems to bootloop.. Im not sure whats happening.. I see the nvidia logo and then reboots again and same..
---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------
The steps I took:
I boot to TWRP first through bootloader.
Format and wipe all partitions basically making it totally fresh.
Then I boot to bootloader and run the flash-all without the reboot continue.
Then I boot back to TWRP and mount system.
Then pull the file and append the line, then push it back.
Then reboot to system.
Now bootloop...
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..

cHECKjAM said:
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
Click to expand...
Click to collapse
-Remove "ro.setupwizard.mode=DISABLED" from (end of file: system/build.prop).
-Try to bootup completely and setup ethernet with internet connection. then power off device.
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
I hope it works.

If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk

mrhamed said:
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk
Click to expand...
Click to collapse
I dont get any method working..
The other thread with the "how to root" is lacking so much details and steps I have no idea how it is supposed to be done..
So I tried flashing the totally default dev image 8.2 . Everything boots and goes in to the setup mode
From there if I unplug ethernet I cant go anywhere.. I then reboot to bootloader and from there boot in to twrp.
Mount the system and modify the prop file as you said. then reboot to system again. Still cant bypass setup.
I also tried the exact same with flashing the vb skip image instead of default vbmeta
same result..
And it is painfully long process and every new try is a pain.
Can you please buddy please:
Write a step by step n exactly how to from scratch:
Flash 8.2 image + root + bypass google setup entirely..

Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Hey buddy..
I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use it until now. So maybe can look in to getting this working during the vacation.
Have you gotten any better idea on how exactly to make this work? I followed all your steps last time and failed twice..

Is there anyone out there except for @mrhamed that has got this method working?
If so please share any real tutorial/steps/guide or whatever that can help.. thanks

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Are you MIA?

EDIT: oops. wrong thread.

8.2.3 - 2019 Pro here, removing ethernet works like a charm.

LifelessLife said:
8.2.3 - 2019 Pro here, removing ethernet works like a charm.
Click to expand...
Click to collapse
Maybe you can explain a bit more?

mrhamed said:
*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
Click to expand...
Click to collapse
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
I think 9.0.0 broke alot of things we have been taking for granted. if not using a Google account is that important to you, best to go ahead and revert back for now.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system

mrhamed said:
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
Click to expand...
Click to collapse
Just pulled the build.prop again and the setupwizard was still disabled. Did a reboot and still requires Google sign in. Guess its back to 8.2.3.

I have no more idea and it should works!
add more options to build props:
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.setupwizard.enable_bypass=1
ro.setupwizard.mode=DISABLED