Good afternoon. I have a big problem. I did root the HTC Hero (GSM) but we did not do and s-off. After several days of relatively normal thing to have restarted it starts but hangs with HTC logo screen and that.
combination works "vol-+ power". the combination "vol + + power" vibrates 3 times, and both green LED lights. combination "home + power" red triangle screen. followed by combination "vol + + power" is the "android system recovery <2e>".
I tried by renaming rom.zip in update.zip, heroboot.zip, etc.. I install the firmware manually, does not work. I tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe pc, RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe, RUU_Hero_HTC_WWE-AFK_3.39.421.3_Radio_63.18.55.06P_6.35.15.14_release_signed.exe etc., all give various error.
Phone features:
F: \ adt-bundle-x86-windows-20130729 \ sdk> fastboot oem boot
...
(Bootloader) setup_tag addr = 0xA0000100 cmdline add = 0x8F084058
(Bootloader) TAG: Ramdisk OK
(Bootloader) TAG: smi ok, size = 32
(Bootloader) TAG: 0x1 hwid
(Bootloader) TAG: 0x20800 skuid
(Bootloader) TAG: hero panel = 0x3
(Bootloader) TAG: engineerid = 0x3
(Bootloader) Device CID is not super CID
(Bootloader) CID is HTC__032
(Bootloader) setting.cid :: HTC__032
(Bootloader) serial number: HT9CRL900044
(Bootloader) commandline from head: no_console_suspend = 1 console = null
(Bootloader) command line length = 361
(Bootloader) active commandline: board_hero.disable_uart3 = 0 board_hero.us
(Bootloader) board_hero.disable_sdcard b_h2w_sw = 0 = 0 = 32 androidbo smisize
(Bootloader) ot.baseband = 6.35.15.11 androidboot.cid = HTC__032 androidboot.
(Bootloader) carrier = HTC-EastEurope androidboot.mid = HERO10000 androidboot
(Bootloader). Keycaps = qwerty androidboot.mode = normal androidboot.serialno
(Bootloader) = HT9CRL900044 androidboot.bootloader = 1.76.0013 no_console_su
(Bootloader) spend = 1 console = null
(Bootloader) aARM_Partion [0]. Name = misc
(Bootloader) aARM_Partion. [1] name = recovery
(Bootloader) aARM_Partion. [2] name = boot
(Bootloader) aARM_Partion. [3] name = system
(Bootloader) aARM_Partion. [4] name = cache
(Bootloader) aARM_Partion. [5] name = UserData
(Bootloader) partition number = 6
(Bootloader) Valid partition num = 6
(Bootloader) 0
(Bootloader) 0
(Bootloader) 69,466,957
(Bootloader) 69,784,520
(Bootloader) 69,007,473
(Bootloader) 7473
fimware 2.1-update1
baseband
63.18.15.06pu_6.35.15.11
kernel
6.2.29-7527f009
htc-kernel @ and18-2 # 1
build
Cl345049 3.36.405.2 release-keys
software
3.36.405.2
Browser
webkit 3.1
http://www.htcdev.com/bootloader/ and root after using the phone in HBOOT menu, prints:
*** UNLOCKED ***
HERO CVT SHIP S-ON
HBOOT-1.76.0013 (HERO10000)
Micropores-010F
PANEL-SYN0104 touc
RADIO-6.35.15.11
Jan 9 2012,15:39:56
anyone has solutions and proposals? I searched the internet similar problems without result
conectarenet said:
Good afternoon. I have a big problem. I did root the HTC Hero (GSM) but we did not do and s-off. After several days of relatively normal thing to have restarted it starts but hangs with HTC logo screen and that.
combination works "vol-+ power". the combination "vol + + power" vibrates 3 times, and both green LED lights. combination "home + power" red triangle screen. followed by combination "vol + + power" is the "android system recovery <2e>".
I tried by renaming rom.zip in update.zip, heroboot.zip, etc.. I install the firmware manually, does not work. I tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe pc, RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe, RUU_Hero_HTC_WWE-AFK_3.39.421.3_Radio_63.18.55.06P_6.35.15.14_release_signed.exe etc., all give various error.
Phone features:
F: \ adt-bundle-x86-windows-20130729 \ sdk> fastboot oem boot
...
(Bootloader) setup_tag addr = 0xA0000100 cmdline add = 0x8F084058
(Bootloader) TAG: Ramdisk OK
(Bootloader) TAG: smi ok, size = 32
(Bootloader) TAG: 0x1 hwid
(Bootloader) TAG: 0x20800 skuid
(Bootloader) TAG: hero panel = 0x3
(Bootloader) TAG: engineerid = 0x3
(Bootloader) Device CID is not super CID
(Bootloader) CID is HTC__032
(Bootloader) setting.cid :: HTC__032
(Bootloader) serial number: HT9CRL900044
(Bootloader) commandline from head: no_console_suspend = 1 console = null
(Bootloader) command line length = 361
(Bootloader) active commandline: board_hero.disable_uart3 = 0 board_hero.us
(Bootloader) board_hero.disable_sdcard b_h2w_sw = 0 = 0 = 32 androidbo smisize
(Bootloader) ot.baseband = 6.35.15.11 androidboot.cid = HTC__032 androidboot.
(Bootloader) carrier = HTC-EastEurope androidboot.mid = HERO10000 androidboot
(Bootloader). Keycaps = qwerty androidboot.mode = normal androidboot.serialno
(Bootloader) = HT9CRL900044 androidboot.bootloader = 1.76.0013 no_console_su
(Bootloader) spend = 1 console = null
(Bootloader) aARM_Partion [0]. Name = misc
(Bootloader) aARM_Partion. [1] name = recovery
(Bootloader) aARM_Partion. [2] name = boot
(Bootloader) aARM_Partion. [3] name = system
(Bootloader) aARM_Partion. [4] name = cache
(Bootloader) aARM_Partion. [5] name = UserData
(Bootloader) partition number = 6
(Bootloader) Valid partition num = 6
(Bootloader) 0
(Bootloader) 0
(Bootloader) 69,466,957
(Bootloader) 69,784,520
(Bootloader) 69,007,473
(Bootloader) 7473
fimware 2.1-update1
baseband
63.18.15.06pu_6.35.15.11
kernel
6.2.29-7527f009
htc-kernel @ and18-2 # 1
build
Cl345049 3.36.405.2 release-keys
software
3.36.405.2
Browser
webkit 3.1
http://www.htcdev.com/bootloader/ and root after using the phone in HBOOT menu, prints:
*** UNLOCKED ***
HERO CVT SHIP S-ON
HBOOT-1.76.0013 (HERO10000)
Micropores-010F
PANEL-SYN0104 touc
RADIO-6.35.15.11
Jan 9 2012,15:39:56
anyone has solutions and proposals? I searched the internet similar problems without result
Click to expand...
Click to collapse
if you want to "S-OFF"( Remove security and CID locks) follow these guide
http://forum.xda-developers.com/showpost.php?p=4529084&postcount=1
Related
I believe I did all the steps correctly but it did not seem to work. May have not done the 'immediate' step quickly enough (fastboot oem boot)? Anyway, i tried it a few more times again without success. I seemed to not be able to write the 3 files equired at the end specifically #2 + 3. Now it says it can't find my fastboot flash zip (I renamed mine soff.zip) but it is there...Thought I would give it and me space for a while before I try again. Anyone with any suggestions?
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
.torrented said:
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Pretty sure I extracted that but will double check, thanks..
rootntootn said:
Pretty sure I extracted that but will double check, thanks..
Click to expand...
Click to collapse
Posting command file here as it did not work again...... I put the zip file and extracted in my working directory not the phone,is that correct? just occured to me that it may need to be on phone sd card anyway below is what got spit out, any help appreciated.
C:\adt-bundle-windows-x86\sdk\platform-tools>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.049s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot flash zip soff.zip
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem boot
...
(bootloader) monarudo_vibrate_device_time(): vibrate 200(ms)...
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) setup_tag addr=0x80600100 cmdline add=0x003147C8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x32401
(bootloader) TAG:hero panel = 0x94005B
(bootloader) TAG:engineerid = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::22222222
(bootloader) serial number: FA2BAS504674
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=dlx user_debug=31
(bootloader) command line length =796
(bootloader) active commandline: poweron_status=1 reset_status=0 board_mo
(bootloader) narudo.disable_uart3=0 diag.enabled=0 board_monarudo.debug_u
(bootloader) art=0 userdata_sel=0 androidboot.emmc=true androidboot.pages
(bootloader) ize=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.s
(bootloader) f=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.
(bootloader) ofs=694 imc_online_log=0 androidboot.efuse_info=SNSL androi
(bootloader) dboot.baseband=1.00.00.1023_3 androidboot.cid=22222222 andro
(bootloader) idboot.devicerev=3 androidboot.batt_poweron=good_battery and
(bootloader) roidboot.carrier=COM
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=extra
(bootloader) aARM_Partion[A].name=radio
(bootloader) aARM_Partion.name=adsp
(bootloader) aARM_Partion[C].name=dsps
(bootloader) aARM_Partion[D].name=radio_config
(bootloader) aARM_Partion[E].name=modem_st1
(bootloader) aARM_Partion[F].name=modem_st2
(bootloader) aARM_Partion[10].name=cdma_record
(bootloader) aARM_Partion[11].name=reserve
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) setting_get_bootmode() = 9
(bootloader) smem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
(bootloader) jump_to_kernel: machine_id(4060), tags_addr(0x80600100), ker
(bootloader) nel_addr(0x80608000)
(bootloader) -------------------hboot boot time:156503 msec
FAILED (status read failed (Too many links))
finished. total time: 2.904s
C:\adt-bundle-windows-x86\sdk\platform-tools>
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
rootntootn said:
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
Click to expand...
Click to collapse
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
.torrented said:
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
Click to expand...
Click to collapse
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
Is it possible I need stock kernal first?
rootntootn said:
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
Is it possible I need stock kernal first?
Click to expand...
Click to collapse
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
CharliesTheMan said:
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
Click to expand...
Click to collapse
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
rootntootn said:
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
Click to expand...
Click to collapse
BINGO! That did it. Thanks for everyones help!!
Hi everyone, help me i need the carrier,
Code:
fastboot oem config
on their Moto E2 3G and tell me the tag you get for the carrier section? Should look like this:
Code:
(bootloader) <UTAG name="carrier" type="str" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see
(bootloader) </description>
(bootloader) </UTAG>
I need what is between the two value tags.
Or if anyone knows what the carrier name would be for the command:
Code:
fastboot oem config carrier <carrier name>
It would be greatly appreciated! Thanks
Hi everyone, help me i need the carrier,
Code:
fastboot oem config
on their Moto E2 3G and tell me the tag you get for the carrier section? Should look like this:
Code:
(bootloader) <UTAG name="carrier" type="str" protected="false">
(bootloader) <value>
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see
(bootloader) </description>
(bootloader) </UTAG>
I need what is between the two value tags.
Or if anyone knows what the carrier name would be for the command:
Code:
fastboot oem config carrier <carrier name>
It would be greatly appreciated! Thanks
I bought a Redmi Note 5 6 months ago.Last night i was watching youtube but I recieved a low battery warning so I paused the video and put mobile in sleep because I didn't wanted to charge it for like 6 hours.Next morning it was switched off I though IT was already low on battery maybe thats why the battery died.So I charged it and turned it on but its not going any further than the MI logo screen.
I have very important data and pics in there thats why I can't format it.Please help me to get back my data.All the pics I took in last 8 years its all in there.Unfortunetely I don't have a backup (Maybe I will have to regret it for the rest of my life or maybe if anyone of you guys can help me so that I don't have to regret it for the rest of my life).Its booting in MI recovery 3.0 which only gives the option to wipe all data and its also booting into fastboot mode.It doesn't have root access and the bootloader is locked.But the data is too important.I am literally crying as I am typing this post.Please HELP ME!!
Somewhere deep inside I know its the youtube temp data which is causing the problem but I don't know what to do.I will do anything just tell me what to do please.Service center clearly said that they can't save the data.You guys are my last HOPE.Please Do Something.Can I do anything through Fastboot Mode.How do they install OTA updates without deleting the DATA.If you guys will help me get my old life back you will for sure go to heaven!!
THANKS!!!
AND DAMN ME FOR NOT TAKING ANY BACKUP . . . .
Hi , you can try to backup your data with Mi Assistant ( Mi PC Suite)
download from here inside your PC:
http://pcsuite.mi.com/
Boot your device into Recovery mode , you should see :
Main Menu
- Recovery
- Wipe Data
- Connect with Mi Assistant ( click on that and plug the USB cable in PC )
Wait for drivers to be installed , and next you have in this post for Backing up data : )...
https://webcazine.com/14790/how-to-back-up-and-restore-your-xiaomi-device-using-mi-pc-suite/
After you do backup , you can Wipe data from recovery or to update your device using Mi PC Suite .
Good Luck : )
Thanks For Replying. You have no idea how much this means to me. . .
Teddy Lo said:
Hi , you can try to backup your data with Mi Assistant ( Mi PC Suite)
download from here inside your PC:
Boot your device into Recovery mode , you should see :
Main Menu
- Recovery
- Wipe Data
- Connect with Mi Assistant ( click on that and plug the USB cable in PC )
Wait for drivers to be installed , and next you have in this post for Backing up data : )...
After you do backup , you can Wipe data from recovery or to update your device using Mi PC Suite .
Good Luck : )
Click to expand...
Click to collapse
I already tried that.But it said device not supported.So I googled it then found out that MI PC suite doesn't support devices over lollipop.Please tell me if you have any other idea.Because you are the only one to even reply to my thread.I thought there is a lot of devlopers here who can easily help me out.But I see no one helping me.If you know someone with more knowledge please discuss this situation with them PLEASE!!
Can I flash stock ROM through fastboot on a locked bootloader without deleting internal storage content??
Please suggest something I can't live with this kind of stress.PLEASE!!
THANKS!!!
Try this :
put your device into fastboot mode, now On PC in fastboot command line write :
fastboot getvar all
You will be looking for version-main the number beside it is your firmware version
Now , once you find it , google on the internet for that firmware , and extract from that firmware just boot.img and flash with fastboot command line like for example:
fastboot flash boot boot.img and press Enter , I'm not 100% sure it will work like that but you can try ...
Teddy Lo said:
Try this :
put your device into fastboot mode, now On PC in fastboot command line write :
fastboot getvar all
You will be looking for version-main the number beside it is your firmware version
Now , once you find it , google on the internet for that firmware , and extract from that firmware just boot.img and flash with fastboot command line like for example:
fastboot flash boot boot.img and press Enter , I'm not 100% sure it will work like that but you can try ...
Click to expand...
Click to collapse
There is no such option like version-main however there is is an option called just version.
This is what it gives . . . .
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) token:nTFW03JTw76SJqewmdnCYQAA
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4232000
(bootloader) variant:QRD eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_DAISY1.0_20180914131349
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd43779e00
(bootloader) partition-type:cust:
(bootloader) partition-size:cust: 0x34000000
(bootloader) partition-type:logdump:
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:dpo:
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:msadp:
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x40000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x40000
(bootloader) partition-type:cmnlib64bak:
(bootloader) partition-size:cmnlib64bak: 0x40000
(bootloader) partition-type:cmnlib64:
(bootloader) partition-size:cmnlib64: 0x40000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x40000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x40000
(bootloader) partition-type:lksecappbak:
(bootloader) partition-size:lksecappbak: 0x20000
(bootloader) partition-type:lksecapp:
(bootloader) partition-size:lksecapp: 0x20000
(bootloader) partition-type:mcfg:
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:syscfg:
(bootloader) partition-size:syscfg: 0x80000
(bootloader) partition-type:mdtp:
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:dip:
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:mota:
(bootloader) partition-size:mota: 0x80000
(bootloader) partition-type:limits:
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-typeem:
(bootloader) partition-sizeem: 0x10000000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0xb00000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-typeDR:
(bootloader) partition-sizeDR: 0x8000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-type:dsp:
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:devcfgbak:
(bootloader) partition-size:devcfgbak: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x5400000
(bootloader) rollback_ver:0
(bootloader) serialno:8a7dd21a0904
(bootloader) kernel:lk
(bootloader) product:vince
all:
finished. total time: 1.172s
Click to expand...
Click to collapse
Please tell me what should I do now?
I even raised the guts to try fastboot erase cache But it said that the device is locked.I tried to flash twrp which I knew I can't on a locked bootloader still I tried but it said Partition flashing is not allowed.So I literally can't do ****.
Hi you have Xiaomi Note 5 also know as Xiaomi Note 5 Plus
MIUI Version 10
Security Patch : 2018.09.14
Code Name is : vince
Probably Redmi Note 5 India (MEl7) version
I didin't find any of those firmare with security patch 2018.09.14 in order to use the same boot.img in order to try to boot your device normaly .
But you can try this one :
https://ufile.io/cw9x3
flash with fastboot , or try to boot with fastboot
like fast bootboot boot boot.img ....
aasifehsan said:
I bought a Redmi Note 5 6 months ago.Last night i was watching youtube but I recieved a low battery warning so I paused the video and put mobile in sleep because I didn't wanted to charge it for like 6 hours.Next morning it was switched off I though IT was already low on battery maybe thats why the battery died.So I charged it and turned it on but its not going any further than the MI logo screen.
I have very important data and pics in there thats why I can't format it.Please help me to get back my data.All the pics I took in last 8 years its all in there.Unfortunetely I don't have a backup (Maybe I will have to regret it for the rest of my life or maybe if anyone of you guys can help me so that I don't have to regret it for the rest of my life).Its booting in MI recovery 3.0 which only gives the option to wipe all data and its also booting into fastboot mode.It doesn't have root access and the bootloader is locked.But the data is too important.I am literally crying as I am typing this post.Please HELP ME!!
Somewhere deep inside I know its the youtube temp data which is causing the problem but I don't know what to do.I will do anything just tell me what to do please.Service center clearly said that they can't save the data.You guys are my last HOPE.Please Do Something.Can I do anything through Fastboot Mode.How do they install OTA updates without deleting the DATA.If you guys will help me get my old life back you will for sure go to heaven!!
THANKS!!!
AND DAMN ME FOR NOT TAKING ANY BACKUP . . . .
Click to expand...
Click to collapse
If you can boot to recovery, you can wipe the cache partition, that will remove the temporary data. If there were any stock OTA updates released for the device, you can manually download the update and flash it via stock recovery via adb if your stock recovery has the "apply update from adb" or via sdcard if your recovery has "apply update from sdcard"
Note: this will not work with the full stock firmware file that is meant to be flashed via flashtool using PC, it has to be an official OTA update.zip in downloadable form.
Using fastboot isn't going to work unless you unlock your bootloader and if you unlock it that will wipe your data.
Sent from my LGL84VL using Tapatalk
I don't know your device, or if it is even possible while in some kind of bootloop. But try searching if its possible to boot into safe-mode.
Hello all, same problem.. Please if you have recovered data than tell me.
Hello all, I have also same problem. While watching YouTube my Redmi note 5 pro freezed. So I restarted and it stucked on mi logo. I tried recovery option by pressing volume up+power button , but it still came to mi logo. Only it shows fastboot. While charging it shows charging icon.
I tried mi flash tool but it shows flash xbl error.
Please help me soon.. I have important data in it of my exams. I don't have backup.
Xiaomi should also take a note on this.
Hello I have also same problem
There is important data and i am stuck on mi logo
i cant wipe data
if anyone have recovered the data plz plz give solution
Droid6pro said:
Hello I have also same problem
There is important data and i am stuck on mi logo
i cant wipe data
if anyone have recovered the data plz plz give solution
Click to expand...
Click to collapse
If you can access the phone by means of ADB then you may have a chance.
Interesting to see if it can be recovered.
If you do recover it, suspect malware is present.
Physically isolate phone/recover data from critical data drives.
I would have wrote it off by now... I've lost important data in other ways.
Learning from this is may be all you can do.
Always assume a OS drive will fail without warning... as well as the attached data drive.
Best wishes.
Based on the below bootloader information and the 'ls -l /dev/block/platform/mtk-mdsc.0/by-name' results, can anyone help me understand whether I am able to copy a new boot or recovery image to my generic MediaTek tablet using dd. I am able to access fastboot, but fastboot doesn't seem to have very many commands available, or it has proprietary fastboot commands specific to this generic device. In fact, there is a dedicated partition named 'flashinfo' that I can copy using dd but I do not know how to view (decompile) this .img file. I have pulled an .img file from every partition if this would be helpful to someone willing to take the time to help me out. Any direction would be greatly appreciated.
############################
Bootloader Information:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ff000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2360000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizeersist: 3000000
(bootloader) partition-typeersist: ext4
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: ALONG8163_E_86VM
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
How do I unlock this bootloader? Can I use dd to replace a partition based on the bootloader data provided? Notably I tried using dd to copy a Magisk_Patched.img to the boot partition, but both efforts resulted in a bootloop
(I also noticed that the lk (Linux Kernel) and boot partitions are distinct on this device. Is this unusual? Is it possible that this is why Magisk is not working?)
###########################
Results from 'ls -lF /dev/block/platform/mtk-mdsc.0/by-name':
please post in proper sections questions go to q/a
Is this a Hiteker tablet?
If so I have got the same tablet, rooted it, and installed TWRP
Still having OTG driver issues.
Yes
Would you share the TWRP image?
Twilight Time said:
Is this a Hiteker tablet?
If so I have got the same tablet, rooted it, and installed TWRP
Still having OTG driver issues.
Click to expand...
Click to collapse
Yes.
Would you share the TWRP image?
excaliber8878 said:
Based on the below bootloader information and the 'ls -l /dev/block/platform/mtk-mdsc.0/by-name' results, can anyone help me understand whether I am able to copy a new boot or recovery image to my generic MediaTek tablet using dd. I am able to access fastboot, but fastboot doesn't seem to have very many commands available, or it has proprietary fastboot commands specific to this generic device. In fact, there is a dedicated partition named 'flashinfo' that I can copy using dd but I do not know how to view (decompile) this .img file. I have pulled an .img file from every partition if this would be helpful to someone willing to take the time to help me out. Any direction would be greatly appreciated.
############################
Bootloader Information:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ff000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2360000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizeersist: 3000000
(bootloader) partition-typeersist: ext4
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: ALONG8163_E_86VM
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
How do I unlock this bootloader? Can I use dd to replace a partition based on the bootloader data provided? Notably I tried using dd to copy a Magisk_Patched.img to the boot partition, but both efforts resulted in a bootloop
(I also noticed that the lk (Linux Kernel) and boot partitions are distinct on this device. Is this unusual? Is it possible that this is why Magisk is not working?)
###########################
Results from 'ls -lF /dev/block/platform/mtk-mdsc.0/by-name':
Click to expand...
Click to collapse
You can push the image using dd. I have replaced the system, boot, and recovery img using this method. I used a gen 2 tablet with Material Terminal to connect using adb. You first have to put the adb keys in the root of the gen 2 tablet to connect to a gen 3. Let me know if this helps
excaliber88787 said:
Yes Would you share the TWRP image? Yes. Would you share the TWRP image?
Click to expand...
Click to collapse
excaliber88787 said:
Yes Would you share the TWRP image? Yes. Would you share the TWRP image?
Click to expand...
Click to collapse
Twilight Time said:
You can push the image using dd. I have replaced the system, boot, and recovery img using this method. I used a gen 2 tablet with Material Terminal to connect using adb. You first have to put the adb keys in the root of the gen 2 tablet to connect to a gen 3. Let me know if this helps
Click to expand...
Click to collapse
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Twilight Time said:
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Click to expand...
Click to collapse
Twilight Time said:
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Click to expand...
Click to collapse
excaliber88787 said:
Yes
Would you share the TWRP image?
Yes.
Would you share the TWRP image?
Click to expand...
Click to collapse
hey did you ever get to change your os on your tablet?if so i got same1 can you assist
excaliber88787 said:
Would you share the TWRP image?
Click to expand...
Click to collapse
port for Alldocube iplay10 pro Android 9 sdk 28 display res 1200*1920 proc MT8163 kernel Linux version 4.9.117 ([email protected] // TWRP 3.0.2
ro.sf.lcd_density=240
ro.sf.hwrotation=0
busybox is static from Android 9
-----------------------------------------
donor teclast A10S Android 7.1.2 sdk 25 display res 1200*1920 proc MT8163 kernel Linux version 3.18.35 ([email protected]// TWRP 3.3.1
ro.sf.hwrotation=180
------------------------------------------
donor Teclast P80h (D4C5) TWRP 3.0.2-1 tablet is Android 5.1 sdk 22 kernel Linux version 3.10.72 ([email protected] ... and display res 1280*800 proc MT8163 // TWRP 3.0.2-1
ro.sf.hwrotation=0
10.91 MB file on MEGA
mega.nz
---------------------------------------
port for U804mc . tablet is Android 5.1 sdk 22 kernel Linux version 3.10.72 ([email protected] ... and display res 1024*600 proc MT8163 // recovery-P80Hv5.img // TWRP 3.0.2
MTK Header
ro.sf.lcd_density=160
ro.sf.hwrotation=180
---------------------------------------
donor Alldocube iPlay 10 . tablet is Android 6. sdk 23 kernel Linux version 3.18.22 . ... and display res 1920*1080 proc MT8163 // TWRP 3.1.1
MTK Header
ro.sf.lcd_density=280
-------------------------------------
port for Alldocube iPlay 8 . tablet is Android 6. sdk 23 kernel Linux version 3.18.22 . ... proc MT8163 // TWRPi8 3.1
MTK Header
ro.sf.lcd_density=180
------------------------------------------
donor Aquaris_M8 tablet is Android 6 //display res 1280 x 800 // proc MT8163 // twrp-3.6.2_9-
ro.sf.lcd_density=180
Download twrp-3.6.2_9-0-Aquaris_M8.img
Download page for twrp-3.6.2_9-0-Aquaris_M8.img
dl.twrp.me
----------------------------------------
port for Alldocube iplay10 pro Android 9 sdk 28 display res 1200*1920 proc MT8163 kernel Linux version 4.9.117 ([email protected] // TWRP 3.3.1
ro.sf.lcd_density=240
ro.sf.hwrotation=0
busybox is static from Android 9
---------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 8.0 Z380M (locked bootloader ok)
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader...
forum.xda-developers.com
donor Asus ZenPad 8.0 Z380M tablet is Android 7 sdk 25 //display res1280x800 // proc MT8163 // kernel Linux version 3.18.35+ ([email protected]) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Jan 12 13:14:25 CST 2018 // TWRP 3.2.1
ro.sf.hwrotation=0
MTK Header
-------------------------------------------------
[RECOVERY] TWRP for Onn Android Tablets (unofficial) - 2019-11-30
TWRP Custom Recovery for the Onn Android Tablet series This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you...
forum.xda-developers.com
donor Android 9 sdk 28 proc MT8163 // twrp 3.3.1_9
ro.sf.hwrotation=270 landscape
----------------------------------------------
port for Alldocube iplay10 pro Android 9 sdk 28 display res 1200*1920 proc MT8163 kernel Linux version 4.9.117 ([email protected] // TWRP 3.3.1
ro.sf.lcd_density=240
ro.sf.hwrotation=0
replace /sbin/libminuitwrp.so for hwrotation=0
Thanks for your help
I'll try it
Hello
Can you email me when you get a chance??
I really want to hear from you.
[email protected]
Twilight Time said:
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Click to expand...
Click to collapse
Are you doing good??
Hopefully you can get a chance to say hello soon...
Da3mo9z said:
Thanks for your help
I'll try it
Click to expand...
Click to collapse
Did you make a backup? unlock your tablet? If you give me the link to your firmware on google disk I'll try to help you with TWRP.....I need stock recovery boot scatter and some files, depends on your Android version