Related
I have a T-Mobile compact IV with the following system:
ROM: 1.37.114.3 NLD
ROM date: 06/20/08
Radioversion:1.00.25.03
Protocolversion: 52.26a.25.09U
Before flashing another ROM I want to dump the original, using pdocread. Reading the device went OK, but the problem came with verifying. The read (pdocread -l) shows the following:
210.50M (0xd280000) DSK1:
| 3.12M (0x31f000) Part00
| 4.38M (0x460000) Part01
| 110.13M (0x6e20000) Part02
| 92.88M (0x5ce0000) Part03
3.75G (0xf0000000) DSK7:
| 3.75G (0xf0000000) PART00
STRG handles:
handle 27198516 3.75G (0xf0000000)
handle 87ca38da 92.88M (0x5ce0000)
handle 07db27be110.13M (0x6e20000)
handle c7db279a 4.38M (0x460000)
handle a7db2752 3.12M (0x31f000)
disk 27198516
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 87ca38da
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 07db27be
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c7db279a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a7db2752
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A verify of Part 2 however (pdocread -w -d DSK1: -p Part02 -t) showed the following:
real nr of sectors: 1 - 512.00byte, 0x200whereas I expected something like
real nr of sectors: xxxxx - 110.13Mbyte (0x6e2000)
The same result was obtained when verifying the other parts.
I checked itsutils.log for a line referring to block size (e.g. STOREINFO dev='Name' store='StoreName' nsect=2dd9 bpsect=1000 free=0 maxpartsize=0), but no such line exists in that log.
What have I done wrong or should I do? I cannot now give the correct instructions to pdocread to dump the ROM.
use blocksize -b 0x800
pdocread -h XXXXX -w -b 0x800 -t
or
pdocread -d DSK1: -p Part02 -b 0x800 -w -t
willem
Thanks Willem. I tried and it works as expected.
After my post (it's alwards afterwards) I found the following thread which also mentions 0x800: http://forum.xda-developers.com/showthread.php?p=2460483#post2460483
Topic closed I'd say.
Im trying to dump my rom before flashing another.
Im using the instructions from here:
http://forum.xda-developers.com/showpost.php?p=3078601&postcount=4
However when i get to step 6 i get the following error:
"ERROR: ITReadDisk: outbuf ==NULL
- The device is not ready for use."
Cam someone please help me, i've tried searching but can not find a solution.
Getting the same error - please help us
I am getting the same Device not ready error. Here's what I get from running pdocread.exe -l
Code:
C:\itsutils>pdocread.exe -l
209.50M (0xd180000) DSK1:
| 3.12M (0x31f000) Part00
| 4.50M (0x480000) Part01
| 79.63M (0x4fa0000) Part02
| 122.25M (0x7a40000) Part03
3.69G (0xec000000) DSK7:
| 3.69G (0xec000000) PART00
STRG handles:
handle e7a46f96 3.69G (0xec000000)
handle 87ab74a6122.25M (0x7a40000)
handle a7bb2136 79.63M (0x4fa0000)
handle 47bb2112 4.50M (0x480000)
handle 87bb20ca 3.12M (0x31f000)
disk e7a46f96
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 87ab74a6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a7bb2136
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 47bb2112
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 87bb20ca
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\itsutils>pdocread -w -d FLASHDR -b 0x800 -p Part00 -t
real nr of sectors: 1 - 2.00kbyte, 0x800
C:\itsutils>pdocread -w -d DSK1 -b 0x1000 -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
ERROR: ITReadDisk: outbuf==NULL
- The device is not ready for use.
Please help.....
After fighting versus the Tattoo for 2 hours I have finally flashed the device successfully.
Since there is not a proper thread containing the exact procedure for this device I'm going to explain it a little bit in detail, specially based on this device different things that doesn't have other android phones:
1. First we need to find a micro SD, normally this device comes with a 2gb Sandisk micro SD, this will be fine.
2. We need to format the microSD to FAT32, so remember to save your files before going on.
3. After the format, we need to create a GoldCard with this SD Card. Basically this is a "transformation procedure". You can find the method here: http://forum.xda-developers.com/showthread.php?t=572683 but I'm going to explain it based on Tattoo
Creating the Gold Card:
4. We need the android-sdk tools, we can find them here: http://developer.android.com/sdk/index.html download them, and unzip in a folder maybe in C:\androidtools
5. Go the the Command line (Start->Execute->write cmd and OK), and there you should find where you unzip the android-sdk tools, example cd c:\androidtools\tools
6. Run this command "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" if you had the microSD in the drive you will find a long number like:
532600bd227d9c0347329407514d5402
7. Go to this page to reverse it: http://hexrev.soaa.me/ and copy the code reversed:
In our example it will be: 00544d5107943247039c7d22bd002653
8. Go to this page to generate your GoldCard image: http://psas.revskills.de/?q=goldcard
And put your reversed number and you email. You will receive an email with a file called "goldcard.img"
9. Now you need an Hex editor like HXD. Download it from: http://download.cnet.com/HxD-Hex-Editor/3000-2352_4-10891068.html?tag=mncol
10. Exactly the same as the instructions I pasted above:
11. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
12. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK. (BEWARE, MUST BE UNDER PHYSICAL DISK NOT LOGICAL DISK, THIS MISTAKE MADE ME BIG PROBLEMS)
13. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
14. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
15. Click on the “removable disk” tab. Select offset (line) 00000000 till offset (line) 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
16. Click on File > Save. now you can exit the program.
------------
17. Now with the gold card created (the microSD transformed) we must reboot the HTC Tattoo. When we press the "reboot" button we must press nearly at the same time the POWER OFF and VOLUME DOWN buttons at the SAME TIME!!!! He will enter a new menu called HBOOT
18. We press back button to go to fastboot USB mode
19. Now we have to start the flashing utility for example: http://rapidshare.com/files/292517090/RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe
This is done the 19th Decembre 2009, but maybe on the future there will be newer flash releases so this file will be replaced for the newer one.
19.1 If we get either Error 170 or 171 in the flashing process follow this other guide to solve this issue: http://forum.xda-developers.com/showthread.php?t=646663
20. The Flash will start we must wait, its better to do this process with 100% battery left
21. After 10 minutes, the flash will be done, and the HTC will reboot automatically with the Flashing done and everything OK!
-----------------------
Latest Official WWE Flashes for HTC Tattoo:
19.12.2009: http://rapidshare.com/files/292517090/RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe
This is for all brand of HTC Tattoo? or only Orange?
can get root?
I have successfully flashed my tattoo with your tutorial but still can't use my Wind (italian) sim. At every roboot it ask me the unlock code, says "network succesful unlocked" and after it continue to say "unlocking sim card", but it never stops!!
The data of my phone are those:
HBOOT-0.52.0001
MICROP-0203
RADIO-3.35.07.20
What can I do??
Tony2k do you have your simlock unlock code? Or did you just flash your rom hoping for the simlock to go away?
I have bought the unlock code but the problem it's that I can enter another code, like 12345678, and have always the message "network unlocked successful" and after it continue to say "unlocking sim card", exactly like with code that I have bought.
Well Tony I am sorry but I cant help you here. I dont know whats wrong. I know that you have few trials to enter the simlock unlock code and that after exceeding these attempts you will have to remove the simlock via USB cable (I dont know which software to use). What you can try is using a turbo sim that you can get off ebay. I dont give you my word that it will work, but I have seen one or two people saying that it worked with the tattoo locked to orange uk. If ever you decide to try using the turbo sim, let me know if it bypasses the simlock on the tattoo.
Good luck man.
Great work MiSSigNNo.... u managed to carry out this impossible work as of now with success....
i have few questions to ask you. what made you flash your tattoo???
what advantage do you have at present over the previous ROM???
have u got into superuser mode with this procedure???
i am sure we all would like to know answers for these from you.... please be kind enough to reply to my post....
Manuvaidya:
1. To remove simlock successfully on orange uk htc tattoo, you are forced to flash the rom
2. If you were on orange uk, you will have an android with all the software that orange removed and it will be debranded. And knowing that it can be flashed this will encourage ppl to cook roms.
3. Unfortunately there is no way yet to get root access on the tattoo
Hope this helps you out mate
manuvaidya said:
Great work MiSSigNNo.... u managed to carry out this impossible work as of now with success....
i have few questions to ask you. what made you flash your tattoo???
what advantage do you have at present over the previous ROM???
have u got into superuser mode with this procedure???
i am sure we all would like to know answers for these from you.... please be kind enough to reply to my post....
Click to expand...
Click to collapse
No advantages actually, simply I hate much the mobile-branded roms. Also I tried my sim before I flashed to enter the unlock code and nothing happened, but after, I tried and then it asked me for the unlock code and I could manage to make it successfully.
I don't have the root-superuser mode. I'm sure there are plenty of opportunities with that, but we must look forward on finding the method to make it.
By the way In my "experience" with past branded-roms, they used to be slower since they had plenty of ****ty apps of the brand to make you spend money, and waste unnecesarily memory from the device, this is why the first two things I do everytime I buy an HTC is to flash to default rom and unlock them Since it was more difficult than other times with WM I decided to make this mini-guide, to help others make it easier.
Hi Guys,
I got to the last stage of this walkthrough and when i run the exe for the ROM i get an error 170 on the USB cable. Do you have any ideas what this could be?
Thanks
James
apie2004 said:
Hi Guys,
I got to the last stage of this walkthrough and when i run the exe for the ROM i get an error 170 on the USB cable. Do you have any ideas what this could be?
Thanks
James
Click to expand...
Click to collapse
You didn't make the goldcard correctly. start from the beginning on the goldcard creation. to know if gold card is well created when entering hboot, press the unlock button (call button if i can remember) and there you will se a green message like "key is OK" if not well made there will be a message in red saying "key error" or something like that
Thanks for that guys, still no luck though . I think I might be doing something wrong so here are the results i get as i go along.
adb shell =035344535530324780010f90d4009868
reverse code=009800d4900f01804732305553445303
goldcard.img=
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 41 30 30 00 00 00 00 00 00 00 2C 00 00 00 00 00 00 00 00 00 00 06 00 00 23 00 00 00 00 00 00 00 00 00 68 00 00 00 00 00 00 00 13 00 00 00 84 00 00 00 00 00 00 00 00 00 00 00 00 24 00 00 00 00 00 00 00 18 00 00 29 00 00 00 00 00 FA 00 00 BE 00 00 00 00 19 00 00 00 00 00 00 43 2B BA AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 21 FF FF FF FF FF FF FF FF 00 00 00 00 53 41 30 30 00 00 00 EF 00 83 80 00 00 3B 00 00 52 00 00 71 00 00 00 00 00 00 04 00 00 09 00 00 38 00 00 00 00 B4 83 00 00 5E 00 00 00 00 00 00 00 07 00 00 00 00 D2 00 00 00 00 20 00 45 3B 00 00 00 81 00 00 00 00 00 DD 00 98 06 00 00 00 00 00 00 DE 00 00 00 00 00 3B 00 3C 00 82 53 5A 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I keep getting the same results over and over again so I think I might be going wrong somewhere... Any more ideas?
I'm afraid I'm stuck near the very beginning.
When I navigate to the sdk tools folder and run the command, I get the following:
Code:
C:\android-sdk-windows\tools>adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Is there something I'm doing wrong? I'm running Win 7 x64 and trying to flash a Vodafone branded HTC (build number is apparently "1.67.161.5 CL#74011 release-keys").
Edit: I did format the card to FAT32 like you said.
I found that you need the andriod drivers installed for adb shell to work, if you run SDK setup in the andriod sdk folder and install the driver component, then point the device in device manager towards the new downloaded folder, should be called usb_driver. Hope that helps
Well I tried opening SDK Setup but all that happened was a command prompt window just appeared and then disappeared almost instantly (with Windows then complaining that the program might not have installed correctly). I also tried running it as administrator but got the same result. And nothing happens when I try opening it with cmd.
apie2004 said:
Thanks for that guys, still no luck though . I think I might be doing something wrong so here are the results i get as i go along.
adb shell =035344535530324780010f90d4009868
reverse code=009800d4900f01804732305553445303
goldcard.img=
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 41 30 30 00 00 00 00 00 00 00 2C 00 00 00 00 00 00 00 00 00 00 06 00 00 23 00 00 00 00 00 00 00 00 00 68 00 00 00 00 00 00 00 13 00 00 00 84 00 00 00 00 00 00 00 00 00 00 00 00 24 00 00 00 00 00 00 00 18 00 00 29 00 00 00 00 00 FA 00 00 BE 00 00 00 00 19 00 00 00 00 00 00 43 2B BA AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 21 FF FF FF FF FF FF FF FF 00 00 00 00 53 41 30 30 00 00 00 EF 00 83 80 00 00 3B 00 00 52 00 00 71 00 00 00 00 00 00 04 00 00 09 00 00 38 00 00 00 00 B4 83 00 00 5E 00 00 00 00 00 00 00 07 00 00 00 00 D2 00 00 00 00 20 00 45 3B 00 00 00 81 00 00 00 00 00 DD 00 98 06 00 00 00 00 00 00 DE 00 00 00 00 00 3B 00 3C 00 82 53 5A 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I keep getting the same results over and over again so I think I might be going wrong somewhere... Any more ideas?
Click to expand...
Click to collapse
I also tried a couple of other cards, one broke the card and hboot was really unresponsive. The first card did the same sort of thing, CID error or similar
Success!
I read through this guide about getting adb to work, replaced the current driver with the one linked to there and then also realised that you couldn't get adb to work while the phone was in 'Disk Drive' mode (what a n00b I am). The only way I could get into 'USB Debugging' was by choosing 'HTC Sync' on the phone (but not actually have HTC Sync open on my PC). Once I did that, adb worked properly.
I'm guessing my mistake was just not having the phone in 'USB Debugging', so the old driver would probably have worked as well but at this point I don't really care.
Anyway, I managed to follow the rest of your guide just fine, MiSSigNNo, and it worked! Though I think maybe you should rewrite point number 17 in your original post; from the way you worded it, I thought there was an actual reboot button, different from the power button. A better wording would be something like: "Switch the phone off. Press the Power button to switch it back on but immediately hold down the Volume Down button after pressing the Power button until the HBoot menu appears (at which point you can let go of Volume Down)"
Otherwise I have no complaints, and I cannot thank you enough for posting the guide. It's so nice to be able to get rid of network branding (even if it was only slight in the case of Vodafone), and have a newer version of the system!
Do you know where we can keep track of the WWE Flash releases? It'd be nice to stay up to date I guess.
Edit: lol silly me, wasn't actually checking the rest of the forum so didn't see the thread on WWE ROM links.
what brand of sd card did you use? It's just that i've read somewhere that sandisk (the one i have) doesnt work as a goldcard. Tried it with one that didnt have a brand on it and that didnt work either
I used a SanDisk (it's the 2GB card that came with the phone) so it can't be true that all SanDisk cards don't work. Not that I know much about these things.
For no create a thread for each custom ROM that is ported for the Fire 7 2017 for don't do off-topic in the original ROM forum I have decided to create this where all the custom ROM'S will be collected for the Fire 7 2017 aka austin.
AVAILABLE ROMS:
LineageOS 12.1
AOSP FIRE NEXUS ROM
A.I.C.P 10
Resurrection Remix Lollipop
FIRE OS REVAMPED
DOWNLOAD LINKS:
LineageOS 12.1
AOSP FIRE NEXUS ROM
A.I.C.P 10
Resurrection Reix Lollipop
FIRE OS REVAMPED
KERNELS:
ANY-KERNEL-AUSTIN
INSTALLATION OF ANY ROM (TWRP):
Boot to TWRP
Wipe cache, data, system and SDcard
Format data
Reboot to recovery
Flash ROM
Flash G-APPS (if needed)
INSTALLATION OF ANY ROM (FlashFire):
Open FlashFire
Click the "+" red button
Click on Wipe and and leave the defaults
Click the "+" red button
Click on Flash Zip or OTA, click on the ROM and "tick" auto-mount
Click the "+" red button
Click on Flash Zip or OTA, click on the G-APPS and "tick" auto-mount
Move Wipe to the top
Click on Flash
SCREENSHOTS OF ROMS:
LineageOS 12.1
AOSP FIRE NEXUS ROM
A.I.C.P 10
Resurrection Remix Lollipop
FireOS Revamped
OTHERS/MISC:
Enable 5Ghz Wifi
Special thanks to:
@k4y0z for the unlock method
@mateo121212 for the "porting files and guide"
@ggow for compile Lineage12.1 and AOSP Fire Nexus ROM
@cbolumar for compile A.I.C.P 10
@ANDROID2468 for make fireos revamped
Rortiz2 said:
...
INSTALLATION OF ANY ROM (FlashFire):
Open FlashFire
Click the "+" red button
Click on Wipe and and leave the defaults
Click the "+" red button
Click on Flash Zip or OTA, click on the ROM and "tick" auto-mount
Click the "+" red button
Click on Flash Zip or OTA, click on the G-APPS and "tick" auto-mount
Move Wipe to the top
Click on Flash...
Click to expand...
Click to collapse
Cool but the flash fire instructions are kinda pointless though
Also when we get roms with a newer Android version it will be impossible to install it with flash fire because flash fire doesn't patch the kernel to make it bootable.
How to enable 5Ghz wifi on fire7 2017 with custom roms.
By default, 5Ghz wifi feature of the chip is turned off. Currently, custom android roms cant enable this.
To re-enable 5Ghz feature, you have to:
1. Boot fire OS ( stock rom or revamped fire OS above)
2. Backup /data/nvram/APCFG/APRDEB/WIFI file.
3. Flash your favourite rom.
4. Write back WIFI file, then reboot.
5. Now you can see 5Ghz wifi SSIDs.
In the WIFI nvram file, address 0x00C5 and 0x00C6 seems to responsible for 5Ghz wifi.
analgeizer said:
By default, 5Ghz wifi feature of the chip is turned off. Currently, custom android roms cant enable this.
To re-enable 5Ghz feature, you have to:
1. Boot fire OS ( stock rom or revamped fire OS above)
2. Backup /data/nvram/APCFG/APRDEB/WIFI file.
3. Flash your favourite rom.
4. Write back WIFI file, then reboot.
5. Now you can see 5Ghz wifi SSIDs.
In the WIFI nvram file, address 0x00C5 and 0x00C6 seems to responsible for 5Ghz wifi.
Click to expand...
Click to collapse
Hi,
i tried to edit that file by myself, but it got everytime overwritten after reboot at my device.
Could you provide me your file for compare pls?
Regards
Beltar
Hi to all,
I have a Fire 7 7th with the twrp installed.
I downloaded the lineageos 12.1, but when I flash through twrp I get an error and the flash is not done.
Has anyone managed to make the flash and need some adjustments?
thank you so much
mixmaxmux said:
Hi to all,
I have a Fire 7 7th with the twrp installed.
I downloaded the lineageos 12.1, but when I flash through twrp I get an error and the flash is not done.
Has anyone managed to make the flash and need some adjustments?
thank you so much
Click to expand...
Click to collapse
What error?
Rortiz2 said:
What error?
Click to expand...
Click to collapse
Hi,
In attach the error that occurred during the flash.
Thanks
mixmaxmux said:
Hi,
In attach the error that occurred during the flash.
Thanks
Click to expand...
Click to collapse
TWRP Error 7 is rather common and infers a mismatch between ROM and device. It can be addressed by adjusting the updater script packaged with the ROM zip.
mixmaxmux said:
Hi,
In attach the error that occurred during the flash.
Thanks
Click to expand...
Click to collapse
Did you flash the system?
Enviado desde mi Mi A2 mediante Tapatalk
Rortiz2 said:
Did you flash the system?
Enviado desde mi Mi A2 mediante Tapatalk
Click to expand...
Click to collapse
sorry but I'm not very experienced.
I followed the instructions in the first post:
Boot to TWRP
- Wipe cache, data, system and SDcard
- Format data
- Flash ROM (file lineage-12.1-20181218-UNOFFICIAL-austin.zip)
lineage-12.1-20181218-UNOFFICIAL-austin.zip.zip file I checked that it is not corrupt
Note: I have flashed the lp-fire-nexus-rom-austin-20180602.zip and the gapps and all is Ok or also the revamp rom and all is OK
many thanks for your support.
Regards
Beltar89 said:
Hi,
i tried to edit that file by myself, but it got everytime overwritten after reboot at my device.
Could you provide me your file for compare pls?
Regards
Beltar
Click to expand...
Click to collapse
XDA says that I have to post 10 messages to enable atatchement. So, plz be patient.
Here is a dump of "WIFI" file from stock fireOS setup.
ADDRESS 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 0123456789ABCDEF
------------------------------------------------------------------------------
00000000 04 01 00 00 00 00 00 00 00 00 00 00 22 22 22 22 ............""""
00000010 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E ................
00000020 1E 1E 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ..
00000030 20 20 20 20 00 00 00 00 00 00 00 00 00 00 01 20 ...........
00000040 1A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000060 00 B8 00 00 00 00 00 00 01 00 00 00 00 00 00 00 .ｸ..............
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000C0 00 00 00 00 01 01 01 26 1B 1C 00 00 00 00 00 00 .......&........
000000D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000100 01 00 00 00 00 00 01 00 04 04 01 00 00 00 00 00 ................
00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000200 AA E4 ｪ
mixmaxmux said:
sorry but I'm not very experienced.
I followed the instructions in the first post:
Boot to TWRP
- Wipe cache, data, system and SDcard
- Format data
- Flash ROM (file lineage-12.1-20181218-UNOFFICIAL-austin.zip)
lineage-12.1-20181218-UNOFFICIAL-austin.zip.zip file I checked that it is not corrupt
Note: I have flashed the lp-fire-nexus-rom-austin-20180602.zip and the gapps and all is Ok or also the revamp rom and all is OK
many thanks for your support.
Regards
Click to expand...
Click to collapse
TWRP keep partitions mounted after wipe. Some images fails to extract on already mounted parititon.
Just reboot after wipe, or unmount system partition from TWRP's mount menu.
mixmaxmux said:
sorry but I'm not very experienced.
I followed the instructions in the first post:
Boot to TWRP
- Wipe cache, data, system and SDcard
- Format data
- Flash ROM (file lineage-12.1-20181218-UNOFFICIAL-austin.zip)
lineage-12.1-20181218-UNOFFICIAL-austin.zip.zip file I checked that it is not corrupt
Note: I have flashed the lp-fire-nexus-rom-austin-20180602.zip and the gapps and all is Ok or also the revamp rom and all is OK
many thanks for your support.
Regards
Click to expand...
Click to collapse
Well I do not know what's happening ... I'll upload the ROM again ...
Rortiz2 said:
Well I do not know what's happening ... I'll upload the ROM again ...
Click to expand...
Click to collapse
Many thanks,
At the moment i have flashed the revamped rom and all is ok.
When you upload the rom i can flashed againg and check.
Many thanks for your support.
Max
Hi OP, Thank you for creating a list of all ported roms for Austin. I recently saw your video on flashing the roms using flashfire. Is it possible for you to upload a video showing how you rooted your device and installed flashfire? I'm sorry for asking this as I'm new to flashing custom roms and I really need your help here. A guide on installing twrp also would be nice.
zork307 said:
Hi OP, Thank you for creating a list of all ported roms for Austin. I recently saw your video on flashing the roms using flashfire. Is it possible for you to upload a video showing how you rooted your device and installed flashfire? I'm sorry for asking this as I'm new to flashing custom roms and I really need your help here. A guide on installing twrp also would be nice.
Click to expand...
Click to collapse
Thanks for watch the video. Yes I can make a video. But its better TWRP.
Enviado desde mi Mi A2 mediante Tapatalk
analgeizer said:
XDA says that I have to post 10 messages to enable atatchement. So, plz be patient.
Here is a dump of "WIFI" file from stock fireOS setup.
ADDRESS 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 0123456789ABCDEF
------------------------------------------------------------------------------
00000000 04 01 00 00 00 00 00 00 00 00 00 00 22 22 22 22 ............""""
00000010 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E 1E ................
00000020 1E 1E 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ..
00000030 20 20 20 20 00 00 00 00 00 00 00 00 00 00 01 20 ...........
00000040 1A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000060 00 B8 00 00 00 00 00 00 01 00 00 00 00 00 00 00 .ｸ..............
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000C0 00 00 00 00 01 01 01 26 1B 1C 00 00 00 00 00 00 .......&........
000000D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000100 01 00 00 00 00 00 01 00 04 04 01 00 00 00 00 00 ................
00000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000200 AA E4 ｪ
Click to expand...
Click to collapse
Thanks, i already managed to enable 5Ghz. At my first tries i only edited 1 byte. But this will be enough to compare now with my file
regards
Christian
analgeizer said:
TWRP keep partitions mounted after wipe. Some images fails to extract on already mounted parititon.
Just reboot after wipe, or unmount system partition from TWRP's mount menu.
Click to expand...
Click to collapse
I have follow your info and the flash of the lineage rom Is All ok!
Flash lineage ok
Flash gapps ok
Flash magisk ok
Many thanks to all for the support.
Max
mixmaxmux said:
I have follow your info and the flash of the lineage rom Is All ok!
Flash lineage ok
Flash gapps ok
Flash magisk ok
Many thanks to all for the support.
Max
Click to expand...
Click to collapse
I'm glad it worked. I have already updated the post and I added that it should be restarted after wipes.
Added Resurrection Remix!
Finnaly got my N7plus bl unlocked.
Got a nice rom that has double tap to turn on the screen.
But... it still has this brightness issue...
Been looking around and found the driver that controls the LEDs is
BOOST_NT50356 or NT50356
Also found the i2c BUS and i2c address on my device:
7 0x11
Code:
busybox_phh i2cdump -y 7 0x11 -f
Tried with full brightness:
Code:
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 01 e9 0c 02 55 00 00 1f 9e 11 00 28 20 20 00 .????U..???.( .
10: 07 35 ff 07 00 00 00 00 00 00 00 00 00 00 00 00 ?5.?............
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
50: 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .?..............
60: 23 b7 8f 05 00 04 04 01 af 23 2a 0d 01 9b 90 39 #???.????#*????9
70: 95 3c a8 60 1f 27 01 35 04 07 00 00 00 00 00 00 ?<?`?'?5??......
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Minimum
Code:
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 01 e9 0c 02 55 00 00 1f 9e 11 00 28 20 20 00 .????U..???.( .
10: 07 35 5a 00 00 00 00 00 00 00 00 00 00 00 00 00 ?5Z.............
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
50: 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .?..............
60: 23 b7 8f 05 00 04 04 01 af 23 2a 0d 01 9b 90 39 #???.????#*????9
70: 95 3c a8 60 1f 27 01 35 04 07 00 00 00 00 00 00 ?<?`?'?5??......
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Notice address 0x12 and 0x13. The only values that I see changing
Relevant info I found:
https://github.com/archie9211/android_kernel_nokia_B2N/issues/1
https://github.com/derflacco/android_kernel_drg/search?q=boost_nt50356&unscoped_q=boost_nt50356
Obvioulsy I tried to manually change the values, but the address is in use.
Unlock the bootloader?
How have you become successful to unlock the bootloader of Nokia 7 plus? Can you please explain in detail!
jahangirbsmrau said:
How have you become successful to unlock the bootloader of Nokia 7 plus? Can you please explain in detail!
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-7-plus/help/root-t3893363/post78764676